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.
Created attachment 5444 [details]
This is based on Case #51873 and forum thread http://forums.xamarin.com/discussion/comment/34346/#Comment_34346
User is unable to deploy to iOS device after updating to 1.8.365.msi
I couldn't reproduce this issue locally.
Tracelogs, mtbserver.log from user is attached along with this bug report
Xamarin.iOS for VS 1.8.365.msi
Created attachment 5445 [details]
This seems related to a Network issue.
à System.Net.Dns.GetAddrInfo(String name)
à System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
à System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
This logging does not indicate an actual failure of our code. It just means that the address/hostname passed to the DNS call was not resolved within the timeout. This can happen for a number of 'normal' reasons, like the hostname being passed in is actually not resolvable, such as bonjour hostnames.
If something has gone wrong, it's elsewhere. I suspect this particular issue, http error code 429, is because the mac and windows machines have clocks which are out of sync.
@Gouri can you confirm Alan's diagnosis re the 429 error?
http error 429 is the same as bug #16184 and the diagnosis there was clocks out of sync.
I could reproduce Error 429 by making windows VM and mac VM clocks out of sync. The error went away on resyncing the clocks.
Error 429 : https://gist.github.com/GouriKumari/219750b5760090fa0cd5
This bug was raised in response to a user. I have also asked him to reply a response to the bug.
@GouriKumari Any updates from the user?
I have updated the deskcase and forum post related to this bug. However still hasn't got a reply from the user.
Thanks Gouri. Given the error code we can assume this was the clock skew issue, and RESOLVE as NORESPONSE (from the desk case).