Bug 44457 - Xamarin only builds Active Architecture
Summary: Xamarin only builds Active Architecture
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 10.0 (iOS10)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2016-09-17 08:22 UTC by Adam
Modified: 2016-09-19 05:41 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Adam 2016-09-17 08:22:29 UTC
After upgrading my Xamarin installation, I could no longer publish to Test Flight, I would get the error "itms-90502: Apps that only contain the Arm64 slice..."

I know that in XCode, if you have "Build Active Architecture Only" - then you get output with only a single bitness. The bitness is that of the attached device.

It appears that the latest Xamarin is now applying "Active Architecture Only" behavior - meaning, that if you build with a device attached to USB, you won't be able to upload to TestFlight unless you have all of the other prerequisites for single-bitness fulfilled.
Comment 1 Rolf Bjarne Kvinge [MSFT] 2016-09-19 05:41:44 UTC
You can disable this behavior by disabling "device-specific builds" in your project's options.