Unsupported Architectures during upload to store

Question

Unsupported Architectures during upload to store

Natalie van Gogh (Hillebrand Gori NL) 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)

0 comments

1 answer

Your answer

Answer 1

Hi @Natalie van Gogh (Hillebrand Gori NL) ,

Thank you for sharing the details and the steps you have already taken. I understand how frustrating a persistent issue like this can be. Let us use your findings to narrow down the cause.

The immediate issue is that libSkiaSharp.framework inside the IPA contains an unexpected x86_64 architecture, which is typically associated with Intel-based simulator builds rather than physical iOS devices. I suggest investigating this architecture issue first, then checking whether the PIE, segment alignment, and encryption errors remain.

Because each .NET for iOS workload requires a specific Xcode version, it would be helpful to confirm the exact SDK, workload, and active Xcode combination. Also, “latest SDK and workload” may not necessarily reflect the versions currently selected for the project, as these can be influenced by a global.json file or workload-set configuration.

Could you run the following commands from the MAUI project directory and share the output?

dotnet –version 
dotnet –info 
dotnet workload list 
dotnet workload –info 
xcodebuild –version 
xcode-select –p

Please also share:

The iOS target framework from the .csproj

The SkiaSharp package versions

Any RuntimeIdentifier or RuntimeIdentifiers entries

The contents of global.json, if present

As a diagnostic test, you can then rebuild the MAUI application project explicitly for ios-arm64:

dotnet publish <your-project.csproj> \ 
-f <your-ios-target-framework> \ 
-c Release \ 
-p:RuntimeIdentifier=ios-arm64 \ 
-p:ArchiveOnBuild=true

Before uploading the new IPA, extract it and inspect the native binary:

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

If it reports only arm64, try uploading the new IPA and check whether the remaining validation errors persist.

If it still reports arm64 and x86_64, please share the command outputs, project configuration, SkiaSharp versions, and new lipo result so we can investigate the native package assets selected during the build.

For now, I would avoid updating or changing additional components until the current environment has been captured.

If you found my response helpful or informative, I would greatly appreciate it if you could follow this guide for your confirmation.

Thank you.