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 and run project (tested in the iPad 2 9.2 Simulator)
## Expected result
App should not crash on launch
## Actual result
An unhandled ObjectiveC exception is received - Full stack trace:
=== Xamarin Studio ===
Version 5.10.2 (build 56)
Installation UUID: 11a26d86-0d21-407a-8da9-8c197ecc0ad1
Mono 4.2.2 (explicit/996df3c)
GTK+ 2.24.23 (Raleigh theme)
Package version: 402020030
=== Xamarin.Profiler ===
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler
=== Apple Developer Tools ===
Xcode 7.2.1 (9548.1)
=== Xamarin.iOS ===
Version: 184.108.40.206 (Business Edition)
Build date: 2016-01-29 16:59:11-0500
=== Xamarin.Android ===
Version: 220.127.116.11 (Business Edition)
Android SDK: /Users/Adam/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
4.0.3 (API level 15)
4.4 (API level 19)
5.0 (API level 21)
5.1 (API level 22)
6.0 (API level 23)
SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.1
SDK Build Tools Version: 23.0.1
Java SDK: /usr
java version "1.8.0_73"
Java(TM) SE Runtime Environment (build 1.8.0_73-b02)
Java HotSpot(TM) 64-Bit Server VM (build 25.73-b02, mixed mode)
=== Xamarin Android Player ===
=== Xamarin.Mac ===
Version: 18.104.22.168 (Business Edition)
=== Build Information ===
Release ID: 510020056
Git revision: bb74ff467c62ded42b7b7ac7fdd2edc60f8647b0
Build date: 2016-01-26 16:24:41-05
Xamarin addins: 8b797d7ba24d5abab226c2cf9fda77f666263f1b
Build lane: monodevelop-lion-cycle6-c6sr1
=== Operating System ===
Mac OS X 10.11.3
Darwin Adams-Retina-MacBook-Pro.local 15.3.0 Darwin Kernel Version 15.3.0
Thu Dec 10 18:40:58 PST 2015
This happens because the project's options "iOS Bundle Signing" | "Custom Entitlements" are empty for "iPhone Simulator" while it specify "Entitlements.plist" for "iPhone".
Without the entitlements the API won't return a container and this you get this native exception.
The same issue occurs even when specifying the entitlements.
It seems to occur at least the first time the app is deployed (try changing to a new sim for example). On subsequent runs it appears to not crash (presumably the app group directory has been created by then).
Here's an Objective-C sample that does not show the same behaviour - on the initial run the directory is created, rather than being nil:
OK, first it is not going to be easy to test someone else's app group project as you do not have their provisioning profiles, app group ids , etc.
I was able to avoid the noted exception and stack trace by creating new app group id, new icloud container ids (for all three projects), a new app ids (that use the preceding group is and icloud container ids), and of course three new provisioning profiles, one for each project.
Then of course you have to set the iCloud Container id for each project to the iCloud container id set up in Apple's portal, and setting the app group id for each project to the one app group id set up in Apple's portal.
Once I had everything set correctly, the project deployed without issue.
So now bug here I can see other than likely incorrect setup. For instance in the test project as is, I had to set the entitlements as Sebasiten noted, but I also had to set the iCloud container ids for all three project (or for two out of three anyway, one was already set.)
Marking as resolved answered.
I think part of the issue is that XVS does not allow setting for setting the iOS Bundle Signing options in the GUI properties editor (bug #38402) so that might be why there was an issue on the customer's end, if the Entitlements were not set on the bundle signing page.
Also it is pointless for me to send the working version since one would still have to do everything I did to get it to work.
From comment 4 above:
s/So now bug here I can see/So no bug here I can see/