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.
Might be related to bug 39320.
My build host has only 2GB main memory but builds and starts quick when debugging on Simulator. With a device as build target, the build and launch process becomes extremely slow. Maybe finally the iOS watchdog kills the app for taking too long to launch.
It first happened after using the HockeyApp SDK on an iPhone 3. With HockeyApp initialization it terminated, without, it launched on the device. In the meantime, after updating Xamarin and XCode, it happens also on an iPhone 5c.
Hi Thomas. As you say, your configuration may be too low to start a process and debug it. The culprit is most likely the iPhone, though, not the Mac. Xcode is generally not well suited for older and low end devices. I'm not sure what to do with this bug, though, since it doesn't seem to provide any actionable items. I'm closing right now as "answered" but do reopen if you feel there's something we can do to help here.
Restarting the iPhone worked for me