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 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.
The attached sample will launch from Xamarin Studio on OSX, but crashes on the simulator with
killed com.app.name[pid 53360] because its use of the get-task-allow entitlement is not allowed (error code -67030)
**Steps to Reproduce:**
1. Run the attached sample in Visual Studio, connected to an iOS build host
2. Deploy to an iOS Simulator
Crashes immediately after launching on the simulator.
**Build Date & Platform:**
I used the Console on the Mac to see the error message.
I have checked this issue via running attached project on VS and getting exception as soon as application launch on simulator.
Debug Log : https://gist.github.com/Mohit-Kheterpal/b7f25124cea47eec90a3
IDE Log : https://gist.github.com/Mohit-Kheterpal/640f2f5aba732e87c09d
Environment info :
Microsoft Visual Studio Professional 2013
Version 12.0.21005.1 REL
Microsoft .NET Framework
Xamarin 18.104.22.168 (4cc27565ba83fc6ad690f708f553e9ba8300898b)
We have made many improvements regarding iOS connection to the Mac and also to the Build and Deployment process, since the bug was reported. We replace the old connection mechanism with a brand new one.
Given that I'm not able to reproduce the issue, I mark this as Resolved, and please feel free to re open it if you still find issues like the reported one.