Unsupported Architectures during upload to store

Question

Unsupported Architectures during upload to store

Natalie van Gogh 0

Hi

Context:
I have an app for ios and android developed with dotnet maui.
Normally during summer time the development stops and I pickup the development during the winter.
I am doing the development and builds on a M2 MacMini in VSCode.
I updated my Mac to 27 (GoldenGate). Running XCode 26.6 (and XCode 27). And the latest dotnet sdk and workload for maui.

I updated my project with the latest packages, did a minor code update and tried to use Transporter to upload to the Store for TestFlight.

The upload fails because it detects a unsupported architecture (x86_64) coming from the libskiasharp.framework in the IPA.

lipo indeed states that the ipa zip contains that architecture.

What is going wrong here, why is this now happening.

I am chasing my tail here.

Thanks

Issue log:

The executable 'Payload/VeloDS.app/Frameworks/libSkiaSharp.framework' is not a Position Independent Executable. Please ensure that your build settings are configured to create PIE executables. For more information refer to Technical Q&A QA1788 - Building a Position Independent Executable in the iOS Developer Library. (90080)

Unsupported Architectures. The executable for VeloDS.app/Frameworks/libSkiaSharp.framework contains unsupported architectures '[x86_64]'. (90087)

n/a (ID: LL4ION2NCOJ5MJJYPACXCGMYIE)

Invalid Segment Alignment. The app binary at 'VeloDS.app/Frameworks/libSkiaSharp.framework/libSkiaSharp' does not have proper segment alignment. Try rebuilding the app with the latest Xcode version. (90209)

n/a (ID: LL4ION2NCOJ5MJJYPACXCGMYIE)

The binary is invalid. The encryption info in the LC_ENCRYPTION_INFO load command is either missing or invalid, or the binary is already encrypted. This binary does not seem to have been built with Apple's linker. (90125)

n/a (ID: LL4ION2NCOJ5MJJYPACXCGMYIE)

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

6 answers

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 1

My solution in the end is to add a section in my csproj which executes the removal of the framework during release build of ios.

    <Target Name="StripSkiaSimulatorSlice"
            Condition="$(TargetFramework.Contains('-ios')) and '$(Configuration)' == 'Release'">
        <Exec Command="xcrun lipo -info &quot;$(AppBundleDir)/Frameworks/libSkiaSharp.framework/libSkiaSharp&quot;" />
        <Exec Command="xcrun lipo -remove x86_64 &quot;$(AppBundleDir)/Frameworks/libSkiaSharp.framework/libSkiaSharp&quot; -output &quot;$(AppBundleDir)/Frameworks/libSkiaSharp.framework/libSkiaSharp&quot; || true" />
        <Exec Command="xcrun lipo -info &quot;$(AppBundleDir)/Frameworks/libSkiaSharp.framework/libSkiaSharp&quot;" />
    </Target>

    <PropertyGroup Condition="$(TargetFramework.Contains('-ios')) and '$(Configuration)' == 'Release'">
        <Platforms>arm64</Platforms>
        <RuntimeIdentifier>ios-arm64</RuntimeIdentifier>
        ...
        <ArchiveOnBuild>true</ArchiveOnBuild>
        <TcpPort>58181</TcpPort>
        <BuildIpa>true</BuildIpa>
        <CodesignDependsOn>$(CodesignDependsOn);StripSkiaSimulatorSlice</CodesignDependsOn>
    </PropertyGroup>

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

1 deleted comment

Comments have been turned off. Learn more

Answer 3

Yashwant Rathore 0

The issue fixed by removing the x86_64 architecture from the SkiaSharp package in the NuGet location on the Mac machine.

Step 1: goto skiasharp.nativeassests.ios location -

        cd ~/.nuget/package/skiasharp.nativeassests.ios

Step 2: cd <skiasharp_version>

Step 3: cd runtime/ios/native/libskiaSharp.framework

Step 4: lipo -remove x86_64 libskiasharp -o libSkiaSharp

And then publish the ios application again:

dotnet publish YOUR_APP.csproj -f net10.0-ios -c Release -p:ArchiveOnBuild=true -p:RuntimeIdentifier=ios-arm64

Yashwant Rathore 0 Reputation points

2026-09-17T18:22:21.6166667+00:00
The issue fixed by removing the x86_64 architecture from the SkiaSharp package in the NuGet location on the Mac machine.

Find the SkiaSharp NuGet package location: find ~/.nuget/packages/skiaSharp -type d | head For example: ~/.nuget/packages/skiasharp/4.152.0/

Locate the libSkiaSharp.framework: find ~/.nuget/packages/skiasharp -name "libSkiaSharp.framework" -print

Check which architectures are currently included: file ~/.nuget/packages/skiasharp/4.152.0/runtimes/ios/native/libSkiaSharp.framework/libSkiaSharp If x86_64 is present, you may see something similar to: Mach-O universal binary with ... arm64 x86_64

Create a backup before modifying the NuGet package: cp -R ~/.nuget/packages/skiasharp/4.152.0 \ ~/.nuget/packages/skiasharp/4.152.0.backup

Remove the x86_64 architecture from the SkiaSharp binary using lipo: lipo -remove x86_64 \ ~/.nuget/packages/skiasharp/4.152.0/runtimes/ios/native/libSkiaSharp.framework/libSkiaSharp \ -o /tmp/libSkiaSharp

Replace the original binary: cp /tmp/libSkiaSharp \ ~/.nuget/packages/skiasharp/4.152.0/runtimes/ios/native/libSkiaSharp.framework/libSkiaSharp

Verify that x86_64 has been removed: file ~/.nuget/packages/skiasharp/4.152.0/runtimes/ios/native/libSkiaSharp.framework/libSkiaSharp Or: lipo -info ~/.nuget/packages/skiasharp/4.152.0/runtimes/ios/native/libSkiaSharp.framework/libSkiaSharp

The output should contain arm64 and should not contain x86_64.

Publish the ios application again

dotnet publish YOUR_APP.csproj -f net10.0-ios -c Release -p:ArchiveOnBuild=true -p:RuntimeIdentifier=ios-arm64

Answer 4

The root cause is almost certainly not SkiaSharp itself — it's that your dotnet publish picked up the simulator slice (x86_64) instead of the device slice (arm64). This is a common side effect after upgrading Xcode to 26.6/27 and pulling a fresh .NET for iOS workload.

Here's what to check, in order:

1. Active Xcode. You have both Xcode 26.6 and 27 installed. Each .NET for iOS workload is validated against a specific Xcode version. If the workload targets 26.x but xcode-select points to 27, the build can produce garbage. Run:

xcode-select -p

Make sure the active Xcode matches the one your workload was built for.

2. Explicitly set the RuntimeIdentifier on publish. This is the key step. Without it, publish may pull simulator assets:

dotnet publish <your-project.csproj> \

Per the official docs, ios-arm64 is the correct RID for a release IPA.

3. Inspect the IPA after building. Unzip and run lipo:

lipo -info Payload/VeloDS.app/Frameworks/libSkiaSharp.framework/libSkiaSharp

If it still shows x86_64, the build is stubbornly pulling the simulator package. In that case, do a clean and rebuild in a fresh folder (no leftover obj/bin). Stale intermediate artifacts can drag in the wrong slice.

4. Check global.json and RuntimeIdentifier in the csproj. If the project hardcodes <RuntimeIdentifier>iossimulator-x64</RuntimeIdentifier> or a global.json pins an old SDK, that will override the command line. Remove anything stale.

5. SkiaSharp / workload mismatch. If after forcing ios-arm64 lipo still reports a fat binary containing x86_64, the version of SkiaSharp.Views.Maui.Controls you're using may not ship a clean arm64 device asset for your iOS target framework. Check the package version and try rolling back to the previous stable release.

The other errors (PIE, Invalid Segment Alignment, LC_ENCRYPTION_INFO) are almost always downstream of the first one — once x86_64 is gone from the IPA, they should disappear. Don't change anything else until lipo -info reports arm64 only.

Natalie van Gogh 0 Reputation points

2026-09-18T18:56:33.24+00:00

xcode-select -p returns Xcode-26.6.0.app which maps to workload 10.0.401 as far as I know

Tried

removing the bin + obj

cleaning the local nuget storage

dotnet clean

Comment

there is no global.json

RunTimeIdentifier in the project is set in the project

<PropertyGroup Condition="$(TargetFramework.Contains('-ios')) and '$(Configuration)' == 'Release'"> <Platforms>arm64</Platforms> <RuntimeIdentifier>ios-arm64</RuntimeIdentifier> <ArchiveOnBuild>true</ArchiveOnBuild> </PropertyGroup>

but the resulting ipa still contains also the x86 version.

I don't want the tinker with the nuget of libskiasharp since the same machine also must build the android version.

Answer 5

kagiyama yutaka 5,410

I think App Store only accepts the device‑safe arm64 slice, and x86_64 in the ipa stops the upload every time, so unzip it and run lipo -info to make sure libSkiaSharp shows arm64 only. and when x86_64 keeps showing up, it means the build picked the simulator slice of SkiaSharp, so publish with RuntimeIdentifier=ios-arm64 in a clean folder to force the correct native assets.

0 comments