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.
Something caused the app to crash instantly, and the debugger still is trying to connect. Here is the build server output:
4] Running tool: EmbeddedResourcesUnpacker
[05-Nov-2013 22:54:54] Running tool: IBTool
[05-Nov-2013 22:54:54] Running tool: InfoPlistBuilder
[05-Nov-2013 22:54:55] Running tool: DebugConfigFileBuilder
[05-Nov-2013 22:54:55] Running tool: DebugSettingsManifestBuilder
[05-Nov-2013 22:54:55] Running tool: PosBuildFixups
[05-Nov-2013 22:54:55] Running tool: OptimizePng
[05-Nov-2013 22:54:55] Running tool: Packager
[05-Nov-2013 22:54:59] stdout: Starting iOS simulator 7.0
ERR: There was an error launching the application: SpringBoard failed to launch application with error: 0
If you upgraded to a build that was built between 2am Thursday 7th and 8pm Thursday 7th this is a known regression that has been fixed.
If that is the case could you close this bug?
Is it ok to close this? I presume that the bug was just the bad build you had as I have not heard back.
James, reopen if it's still happening.
I have checked this issue with following builds:
Xamarin for VS 1.12.247
Application successfully deployed and launched on iOS Simulator as well as on iOS devices using VS and user can stop debugging after clicking on stop debugging.