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. Open the attached sample project.
2. Build to an iPhone Simulator 7.
# Expected Behavior
Starts iOS app in simulator for debugging.
# Actual Behavior
Failed to install $APP$. Connection interrupted:
Created attachment 22868 [details]
Created attachment 22869 [details]
Also worth nothing throughout my Mac build host held a green connection and did not show any disconnects after starting the debug session.
The simulator does not use the words "connection interrupted" this error is being forwarded from mlaunch.
I can't reproduce this on Visual Studio for Mac with the following environment: https://gist.github.com/VincentDondain/a84e7b2cc058b8b890c98752809a57e0
Note: I slightly updated the test case to make it run (SDK version and Launch.storyboard). https://www.dropbox.com/s/1vo33p2abyxjywt/Bug57456.zip?dl=0
This clearly seems Windows-specific and maybe more a VS Windows / Mac host specific problem (:
I'll let Rolf confirm that though (cc'ed).
None of the error messages from mlaunch match this error.
@Pierce, can you still reproduce if you run the same project using Visual Studio for Mac?
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!