Bug 14274 - Mac server remains unreachable after attempting connection
Summary: Mac server remains unreachable after attempting connection
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.6.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2013-08-27 11:36 UTC by PJ
Modified: 2015-01-05 11:19 UTC (History)
8 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 PJ 2013-08-27 11:36:54 UTC

After I entered the PIN and started pairing, the connection dialog didn't tell me it was trying to pair, and my machine returned to the 'Unreachable' state.

while exploring 1.5.234
Comment 1 Dominique Louis 2013-09-16 08:34:34 UTC
Hi Dean,
  I think this may be fixed in the recent builds, but thought I'd confirm with you.
Comment 2 dean.ellis 2013-09-16 08:54:44 UTC
Yup the connection dialog does not work like that any more.
Comment 3 Mohit Kheterpal 2013-11-29 08:43:08 UTC
Today we have checked this issue with following builds :

VS 2013
MTVS 1.10.12

Now we are able to connect to builds host as shown in screencast : http://screencast.com/t/XEZMJconpoEN

This issue does not exist any more. Hence closing this issue.