Steps to reproduce
1. Connect an iPhone 6S with iOS 9.1
2. Create an iOS app with target 9.1
3. Set a breakpoint at AppDelegate.cs FinishedLaunching method
4. Deploy to device
Expected: App is deployed to device with breakpoint set and the breakpoint is hit
Actual: The deployment crashes if a breakpoint is set. Deployment works if breakpoint is removed
XS Info and Logs: https://gist.github.com/cc607cd2a70825fd64b611f2aab84e8b
Application Output: https://gist.github.com/manish-sinha/b0408d129148421a1e1fef1b94235822
Also happens with iOS 9.3 on an iPhone 6S with 9.3
*** Bug 42636 has been marked as a duplicate of this bug. ***
Can you check whenever disabling the 'Enable incremental builds' option in Project Options/iOS Build, then rebuilding fixes the problem ?
I have tried it with disabling incremental builds and even tried disabled incremental builds with all three linker options.
I can still reproduce this issue.
It looks like its reproducible for some people or on some machines, but not on others. So this might be a platform/os specific problem, or a just a problem which happens randomly.
Could somebody add 'Zoltan's Iphone6' to their provisioning profile, and upload the .app directory built with that profile ?
Can reproduce it on tvOS 9.2 device too
Fixed in mono master 941573a76499373f962edb28b0ddb40234b6b2f6. Will backport to 4.6. Thanks for all the help.
This build will hopefully have the fix:
Verified the fix on C8 branch builds
Notice (2018-05-21): bugzilla.xamarin.com will be
switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.
Please join us on
Visual Studio Developer Community and
GitHub to continue tracking
issues. Bugzilla will remain available for reference in read-only mode.
We will continue to work on open Bugzilla bugs and copy them to the new
locations as needed for follow-up. The See Also field
on each Bugzilla bug will be updated with a link to its new location
After Bugzilla is read-only, if you have new information to add for a
bug that does not yet have a matching issue on Developer Community or
GitHub, you can create a follow-up issue in the new location. Copy and
paste the title and description from this bug, and then add your new
details. You can get a pre-formatted version of the title and
In special cases you might also want the comments:
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.