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 for Bug 58052 on
Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
# Steps to reproduce
1. Create an iOS app in Visual Studio.
2. Connect to a Mac via XMA.
3. File -> New another iOS app. At this point, I "lost connectivity". I am showing as no connectivity in XMA or in the toolbar icon.
4. Open Main.storyboard. The file opens, renders correctly, and I can interact with it, even though XMA is saying I am _not_ connected.
# Expected behavior
XMA accurately reflects connection state.
# Actual behavior
XMA doesn't reflect connection state in this weird race condition.
# Supplemental info (logs, images, videos)
# Test environment (full version information)
Environment Info: https://gist.github.com/pierceboggan/363ef465c39316b16a4299e351387165
Created attachment 23456 [details]
Logs from Mac + Windows
Created attachment 23457 [details]
iOS designer working, even though XMA is disconnected
Created attachment 23458 [details]
Created attachment 23459 [details]
Logs from a successful build, even though XMA shows as disconnected
The issue of losing connectivity when changing solutions or projects has been fixed with the following PR and commit hash on master (and pending for approval on 15-4):
- master PR: https://github.com/xamarin/XamarinVS/pull/7794
- master commit: 80073d196d5734bb7c955a0194c5c285c13cc3b9
Related to the different behavior with the designer, this happens because the Designer is not part of XMA anymore. They only uses the SSH layer of XMA, but they have a different and dedicated SSH connection.
What really happens is that the Designer logic is not listening the XMA disconnection (by an unhandled error or because the user decided to disconnect), so if the user opened a storyboard and then disconnects from XMA, they will be able to continue using the storyboard without XMA connected.
Assigning this bug to the Designer team so they can add a mechanism to be aware of the XMA disconnection and also disconnect the designer from the Mac. This will also allow them to not have issues if the user changes the connection to another Mac, etc.
I have reviewed this bug as part of comparing issues in Visual Studio (Windows) with those in Visual Studio for Mac. It appears that there is no equivalent behavior in Visual Studio for Mac because it does not rely on the XMA / build host connection.
The closest potential similarity I saw is if the Xcode path is altered or removed, but Visual Studio for Mac explicitly states that changing this path requires a restart, and it reacts correctly to a valid path vs. an invalid path after restarting; so even then there is no equivalency.