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.
Created attachment 10578 [details]
Xcode submission errors
I am currently attempting to submit WatchKitCatalog to App Store Review and I'm receiving the attached errors on both submission and validation. This could potentially be a sample bug or a WatchKit bug, but seeing as submissions have only been available to the public for about 2 hours, I'm not entirely certain.
The parent app and watch apps have identical build settings: Default SDK, Link SDK assemblies only, support ARMv7 + 64, LLVM enabled, generic value type sharing enabled, and SGen enabled. This was failing in the same way with LLVM and SGen both disabled. I have checked and triple-checked bundle ID names between the apps and the extension.
My Xamarin environment:
=== Xamarin Studio ===
Version 5.8.1 (build 8)
Installation UUID: 0c38ad8a-9e2b-4b47-bc12-c639499efc27
Mono 3.12.1 ((detached/b63df7d)
GTK+ 2.24.23 (Raleigh theme)
Package version: 312010002
=== Apple Developer Tools ===
Xcode 6.2 (6776)
=== Xamarin.Mac ===
Version: 18.104.22.168 (Business Edition)
=== Xamarin.Android ===
Version: 22.214.171.124 (Business Edition)
Android SDK: /Volumes/Infinity Ice Goku the Hedgehog/Users/aaronsky/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
2.1 (API level 7)
2.2 (API level 8)
2.3 (API level 10)
3.1 (API level 12)
4.0 (API level 14)
4.0.3 (API level 15)
4.1 (API level 16)
4.2 (API level 17)
4.3 (API level 18)
4.4 (API level 19)
5.0 (API level 21)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)
=== Xamarin Android Player ===
=== Xamarin.iOS ===
Version: 126.96.36.199 (Business Edition)
Build date: 2015-03-12 15:35:49-0400
=== Build Information ===
Release ID: 508010008
Git revision: f8e52bf493869b6a320a95400553dc9ea8b7ef22
Build date: 2015-03-13 16:16:49-04
Xamarin addins: 84d611cc17567a68daad719327e90af06d2ae327
=== Operating System ===
Mac OS X 10.10.2
Darwin Aarons-iMac.local 14.1.0 Darwin Kernel Version 14.1.0
Thu Feb 26 19:26:47 PST 2015
Still pending backport to monotouch/monotouch-8.8.0-branch (and maccore/monotouch-8.8.0-branch).
@Rolf I tried that build and now it fails to build. https://gist.github.com/aaronsky/c3ff8905dcad53254e9b
For the build issue:
> <Target Name="_GenerateDebugSymbols" Condition="'$(ComputedPlatform)' == 'iPhone'" DependsOnTargets="_CompileToNative"```
> <Target Name="_GenerateDebugSymbols" Condition="'$(ComputedPlatform)' == 'iPhone' And '$(IsWatchApp)' != 'true'" DependsOnTargets="_CompileToNative"
This is a different bug, which is probably only in master.
The other bug from comment 4/5 is in fact related to the previous fix, and has now been fixed in master/macios-cycle5.
@Rolf I made the changes outlined in comment 5 and not only does the app build, it passes all validation tests and was successfully submitted and uploaded to the App Store.
*** Bug 28680 has been marked as a duplicate of this bug. ***
I have checked this issue and now we are not getting this issue with XI 188.8.131.52 as shown in screencast : http://www.screencast.com/t/5nkZCw4iS i.e application loader shows your application is successfully uploaded to itunes store.
Hence closing this issue.
*** Bug 28741 has been marked as a duplicate of this bug. ***
*** Bug 28884 has been marked as a duplicate of this bug. ***