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.
Steps to reproduce this issue:
[Condition: When license is activated and user is logged in]
1. Open VS.
2. Create iOS application.
3. Connect to Mac Server.
4. Observe that VS connected to Mac server properly.
5. Remove internet connection from Mac server.
6. create or open application on VS.
Actual result: 'CONNECT_TO_BUILD_HOST' dialog popup does not appears after
open or create application if connected Mac server is unavailable. However,
when user click 'Start' button or Configure button under iOS Settings,
'CONNECT_TO_BUILD_HOST' dialog displayed properly.
Expected result: 'CONNECT_TO_BUILD_HOST' dialog should appear after open or
create an application if connected Mac server is unreachable.
iOS for VS 1.3.211
This issue is duplicate of Bug 9792 and was verified with MTVS 1.2.121 now I have checked it using MTVS 1.2.121 and latest Xamarin.iOS 6.3.7-185 and Mono 3.1.1-2 and getting same issue on this as well. I am not able to diagnose this issue where the problem is?
REGRESSION: This was verified with MTVS 1.2.121
I think that since this behavior mirrors the behavior outlined in https://bugzilla.xamarin.com/show_bug.cgi?id=9792#c3 we should be ok with this expected behavior. The dialog should appear when you deploy to device (not just on build).
Please update the test cases with this new expected behavior.
As per comment#1 we have updated the test case.
Changing the status of this Issue to Verified