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 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.
I am developing on visual studio 2017 preview from Windows machine. When trying to run simulation on Mac, getting this error message.
"The installed Xamarin.ios (version 10.10) on the Mac test-mbp.hsd.tx.comcast.net is not compatible with the local Xamarin.ios version(10.11). Double click here to select a new server"
Then I tried to install xamarin.ios 10.11 on mac. But I do not see it downloadable from anywhere. Can you direct me to the right place?
Try using the Beta channel on the Mac. The current Alpha is not compatible with Visual Studio Previews.
Could you please explain a little bit? Beta Channel?
On the Mac machine you are connecting to from Windows, you will need to change your "Updates Channel" to Beta, as described here:
After you do this and install the updates on the Mac, you should be able to connect.
Created attachment 23898 [details]
Application UI for simalation
That error went away. However, the application hangs for ever when running it. Please see the attachment above.
Created attachment 23899 [details]
> However, the application hangs for ever when running it. Please see the attachment above.
How often do you see that your app hangs? Do this happen with new projects?
Could you file a new bug for this, since the original issue of this bug is answered here in comment #3
Because we have not received a reply to our request for more information, we are marking this issue as RESOLVED→NORESPONSE. If you are still encountering this issue on the latest Visual Studio 2017, please don’t hesitate to reopen the ticket with the requested information. Thanks!