Bug 60273 - Connection went invalid while waiting for a reply because a mach port died
Summary: Connection went invalid while waiting for a reply because a mach port died
Alias: None
Product: Windows iOS Simulator
Classification: Xamarin
Component: Simulator ()
Version: 1.2
Hardware: PC Mac OS
: --- blocker
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-10-19 17:35 UTC by John Miller [MSFT]
Modified: 2017-10-25 16:02 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Client Log (6.89 KB, text/plain)
2017-10-19 17:35 UTC, John Miller [MSFT]
Server Logs (198.38 KB, application/zip)
2017-10-19 17:36 UTC, John Miller [MSFT]

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description John Miller [MSFT] 2017-10-19 17:35:43 UTC
Created attachment 25371 [details]
Client Log

## Overview

When trying to launch an iOS app, the remoted simulator never finishes launching and shows an error. 

## Additional Information

Attached are the logs.
Reported here: https://forums.xamarin.com/discussion/comment/302629#Comment_302629
Comment 1 John Miller [MSFT] 2017-10-19 17:36:08 UTC
Created attachment 25372 [details]
Server Logs
Comment 2 Alan McGovern 2017-10-19 17:45:50 UTC
A patch for a portion of this is already included in an upcoming d15-4 point release.

In the meantime can you check if the person has any apple Simulator or Xcode running on their paired mac. If it is running, does the problem go away when they quit them.

Also, does it go away if they reboot the Mac?
Comment 3 Jesse Liberty 2017-10-19 22:32:28 UTC
The problem does not go away by restarting the Mac.  Neither the simulator nor XCode was running on the Mac.  The Mac in question is a MacPro (2013).  I also tried it on my MacBook Pro with the same result.
Comment 4 Eric Maupin 2017-10-20 16:06:39 UTC
Did you recently upgrade Xcode? Have you launched it since and accepted any prompts?
Comment 5 Jesse Liberty 2017-10-20 19:26:25 UTC
That was it... I opened XCode, added the "additional products" -- and hey! presto! it is working again.

Comment 6 John Miller [MSFT] 2017-10-25 16:02:03 UTC
Thanks for confirming, Jesse! I'll resolve this as answered since Comment #4 seems to have lead to a resolution.