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.
Created attachment 7934 [details]
Error Message in iOS Simulator
Hi Xamarin Team!
Since working with Xamarin on OS X Yosemite, the iOS Simulator can no longer be started. Xcode 5 and Xcode 6 beta are available and Xcode 5 is set as default using "xcode-select". When launching the iOS Simulator, the message in the attached screenshot is displayed. The error message reads (translated from German):
"Only a single instance of iOS Simulator can be running at a time"
In Console, the following messages are printed which indicate that Xamarin might be interfering:
04.09.14 23:16:13,734 mtouch-64: Bundle (null) does not have an FileProviderModuleClass entry.
04.09.14 23:16:13,796 com.apple.xpc.launchd: (com.apple.xpc.launchd.domain.user.1025) Service "com.apple.iphonesimulator.109656" tried to hijack endpoint "PurpleFBServer" from owner: com.xamarin.monodevelop.188324
04.09.14 23:16:13,797 iPhone Simulator: Failed to check in PurpleFBServer service: 1100
Is this a known issue and is there anything that can be done about it? The Xamarin Forums did not prove to be very helpful on this issue.
We have checked this issue on Yosemite 10.10 preview 7 with Xcode 5.1 and we are also experiencing the same issue, i.e. while launching the simulator the application does not get deployed to the simulator and an error pop-up appears.
A separate issue is already been reported for the same by the Xamarin team.
*** This bug has been marked as a duplicate of bug 14476 ***