Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Steps to reproduce:
1) Download this sample app - https://github.com/olegoid/SubmissionSamples/tree/master/WatchOS
2) Set your certificates and provisioning profiles
3) Build the app in release mode, archive and publish with Application Loader
Submission fails with - https://gist.github.com/anonymous/f6c30b69b9e060e7ad5dbc4f5f6af664
Submission should pass without errors.
Manually edit Info.plist file in archive and re-export *ipa
Fixed in https://github.com/xamarin/xamarin-macios/pull/1092
https://github.com/xamarin/xamarin-macios/commit/37afde6a4369a47373d8de5ea38cac2362e757bc -> "[msbuild] Add watch-companion to UIRequiredDeviceCapabilities for watchOS1 extensions" was actually a 2 part fix.
This first commit introduced a bug where the main app's Info.plist gets the watch-companion key and that's now fixed in PR 1092.
I have checked this issue and observed that the WatchOS sample having iOS app targetting 10.1 provided in bug description is now uploaded successfully to itunes without any error and got the successfull email.
using build xamarin.ios-10.2.1.5_44931ae872db694a03d77f24de757ccd1b15c63a