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 unavailable.
This should probably be a shorter timeout than the main timeout. Right now if you do this you *will* see the timeout after about 2 minutes, but we should ask the user to connect if the server can't be reached basically on the first attempt.
It has 10 attempts at trying to connect to the server and only then does it then pop up the dialog as we are waiting for the server to come online. I can reduce the number of retries to 5 if you like?
There is a importante scenario that we cannot forget.
VS should not bother the user if there is no connection with the Mac,.
People should be able to use Visual Studio without any connection (with no dialogs popping up).
So I think is not a issue do not show the connect to build server until is really necessary (like start debugging).
Well I am thinking that if the user cannot connect to the build host immediately on opening MTVS, there are in a few limited scenarios:
1) The build host is not accessible and will never be (user is in a different location with a Windows laptop)
2) The build host is not accessible but will be accessible in 10-120s (user is booting up the mac or something)
3) The build host is accessible or will be in a few seconds (5s or less)
The current system really only works for 3) - we ping a bit and then connect in a few moments.
For 2) If the user is re-booting, they should probably just see the connection dialog here so they can be notified when the server is ready. They can also choose a different, online server if needed
For 1), the current experience is non-ideal. If we're never going to connect to that server, the user should be shown the connection dialog (to connect to another build host) within a reasonable amount of time.
To me, the ideal expected behavior would be to try the server a few times, and then quickly show the user the build host connection dialog. This will allow for a decent user experience in all 3 cases.
Just thinking about this now, so definitely make sure you agree with my thought process here. This is still a V2 issue, however.
I collided with Jarina here, so I'll update based on comment 3:
Jarina introduces the possibility that we may not want to show the connection dialog when the user is not connected.
As far as I know, the addition of the monotouch.dll should not change any of the existing scenarios' expected behavior, but it's a valid point.
Still, we'd want to either a) Show the connection dialog or b) Show the timeout dialog much sooner, or c) Not show the timeout dialog at all unless we're timing out on a user-initiated action.
With the latest builds:
This issue is not appearing as the user is able to connect with the build host successfully, and the host machine always appears as available, until another user is connected to this machine or the machine is on different network.
SO we can close this issue for now.
With the latest builds:
This issue still exists, as when the user's connected build host is unavailable, and the user tries to create a new iOS application then the user is not prompted to connect to build host (Connect to Build Host pop-up does not appears).
Below is the screencast for the same:
Note: This bug is associated with the test case:
Hence, reopening this issue.
Please retest with latest master.
If connected Mac Host server is unavailable and user try to run any ios application 'CONNECT_TO_BUILD_HOST' window appears to connect with Mac Host server.
Hence, closing this issue. Changing its statue as Verified.