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.
Sometimes, on the "Application Output" window, when I press "command" + "enter" to start debugging, I get the following message:
Starting iOS simulator 7.0
ERR: There was an error launching the application: iOS Simulator failed to install the application.
I was able to create a somewhat reproducible case that I attach, but it might take some minutes for the error to appear.
Steps to reproduce:
1. Load project in xamarin ide
3. Set project Debug > iPhone retina 4-inch > iOS 7.0 (11A465)
2. Press "command" + "enter" to start debuting
3. Click on the "+" button. Application will crash. You will get a SIGSEGV error. If Xamarin.IDE catch the error, click on the debugger continue button to get the SIGSEGV error.
4. Repeat from step 2
Here is my system info:
=== Xamarin Studio ===
Version 4.0.13 (build 38)
Installation UUID: .......
Mono 3.2.3 ((no/8d3b4b7)
GTK+ 2.24.20 theme: Raleigh
Package version: 302030000
=== Apple Developer Tools ===
Xcode 5.0 (3332.25)
=== Xamarin.Mac ===
Xamarin.Mac: Not Installed
=== Xamarin.iOS ===
Version: 220.127.116.11 (Business Edition)
Build date: 2013-04-10 18:05:51-0400
=== Xamarin.Android ===
=== Build Information ===
Release ID: 400130038
Git revision: 07afec667f7be5d0ee511eb7115bbac6377fbae8
Build date: 2013-09-24 08:53:29+0000
Xamarin addins: 61140345a5b109633a94409edcbc7a4c19a425c6
=== Operating System ===
Mac OS X 10.8.5
Darwin .....-MacBook-Pro.local 12.5.0 Darwin Kernel Version 12.5.0
Sun Sep 29 13:33:47 PDT 2013
Created attachment 5153 [details]
The xamarin log files containing the error
Created attachment 5154 [details]
Project to reproduce the error
I tried this for a few minutes, and I never got the error you mention, but I'll have this bug report in mind if I see it in other circumstances.
Once this happens, what do you do to fix the problem? Is it enough to just try running the app again, or do you need to restart simulator/Xamarin Studio/your machine?
Usually running the app again fixes the problem, but sometimes it does not and I have to close/open simulator.
This happens continuously across 2 of my developer machines and on my two dev machines. The app doesn't crash in my case, it just does not launch in the simulator. It's like a lottery when the simulator will actually launch the app.
- Press Build
- Build completes.
- Waiting for debugger to connect...
- Simulator screen goes black - loading the app?
- XS exits debugging after a few seconds with the "ERR: There was an error launching the application: iOS Simulator failed to install the application."
- Simulator goes back to app menu
It's seems there is a problem that randomly happens when the debugger tries to connect to the simulator? May be caused by the iOS 7 simulator?
Xamarin Studio: 4.0.13
Mac: Mountain Lion
Dylan, can you check if anything is written to the system Console app when the app doesn't launch?
I am having this happen regularly.
I get this in Console: "iPhone Simulator: Error communicating with SimulatorBridge: NSInvalidReceivePortException - connection went invalid while waiting for a reply"
Xamarin Studio 4.3.1
This error was randomly seen with older Xcode. AFAIK it was never duplicated but has not been seen for years now (using newer Xcode versions).
If you are still experiencing this issue please provide updated information and re-open the bug report. Thanks!