Bug 52718 - Agent never connected
Summary: Agent never connected
Alias: None
Product: Workbooks & Inspector
Classification: Xamarin
Component: Agent: iOS ()
Version: 1.1.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: xamarininteractive
Depends on:
Reported: 2017-02-23 19:52 UTC by Chris Hardy [MSFT]
Modified: 2017-10-02 17:42 UTC (History)
3 users (show)

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

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 Chris Hardy [MSFT] 2017-02-23 19:52:37 UTC
Whilst trying to repro another issue, the agent never connected to the simulator: https://screencast.com/t/iFTh3REub6O

Comment 1 Sandy Armstrong [MSFT] 2017-02-23 20:28:29 UTC
Is the simulator frozen? I've seen the iOS sim freeze and need restarting before anything works with it.

Does quitting the simulator and trying to open the workbook again cause it the sim to launch, load the app, and connect as expected?
Comment 2 Chris Hardy [MSFT] 2017-02-23 20:35:48 UTC
The simulator seemed fine and just closing and re-opening Workbooks (leaving the Simulator as is) seemed to get things up and running again. So not too sure without it happening frequently if there's too much that can be done here.
Comment 3 Sandy Armstrong [MSFT] 2017-02-23 20:39:11 UTC
If quitting and reopening Workbooks fixed it, it's more likely to be a bug with us, then. Will poke around.
Comment 4 Aaron Bockover [MSFT] 2017-09-11 17:18:05 UTC
We've done quite a bit of work in this area since the last activity on this bug. Would you mind testing with the latest 1.3 in the Beta channel and confirm if this is still an issue?
Comment 5 Aaron Bockover [MSFT] 2017-10-02 17:42:57 UTC
Closing due to no response in a few weeks.