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 58083 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. Connect to a Mac host.
2. Create a new iOS app.
3. Open a storyboard. Drag some items onto the design surface to ensure everything works as intended.
4. Disconnect the Mac. In my case, the connected Mac was powered off.
5. Attempt to continue to interact with the design surface (ex: by dragging controls onto the design surface).
# Expected behavior
Designer agent immediately (with 1-2s) knows that the Mac is no longer available and shows a message to the user.
# Actual behavior
I can continue to drag-and-drop objects onto the design surface, even though the Mac is powered off. I stay in this state for around 15 seconds before the designer recognizes that I have been disconnected and shows the following error:
Message - https://gist.github.com/pierceboggan/67874737f18a039a3718df69518a6e63
Screenshot - https://www.screencast.com/t/3BTEr9KPKge
# Supplemental info (logs, images, videos)
Logs attached. I reconnected to my Mac after this occurred to retrieve those logs as well.
# Test environment (full version information)
Tested with Visual Studio 2017 15.3 Preview 3 - https://gist.github.com/pierceboggan/363ef465c39316b16a4299e351387165
Created attachment 23478 [details]
This bug is related to the bug#58052: https://bugzilla.xamarin.com/show_bug.cgi?id=58052
As mentioned Designer is not part of the XMA process anymore, which causes them to need to hook on some XMA events to refresh their state.
The required changes needs to be done on md-addins probably, so I assign this to Designer team.