Bug 16274 - [iOS-VS] Unable to deploy on iOS device after the latest update to 1.8.365
Summary: [iOS-VS] Unable to deploy on iOS device after the latest update to 1.8.365
Status: RESOLVED NORESPONSE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.8.x
Hardware: PC Mac OS
: High normal
Target Milestone: 1.12 (Merge)
Assignee: GouriKumari
URL:
Depends on:
Blocks:
 
Reported: 2013-11-15 13:06 UTC by GouriKumari
Modified: 2015-01-05 11:21 UTC (History)
10 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Trace.log (12.63 KB, application/octet-stream)
2013-11-15 13:06 UTC, GouriKumari
Details
mtbserver.log (296.44 KB, application/octet-stream)
2013-11-15 13:06 UTC, GouriKumari
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED NORESPONSE

Description GouriKumari 2013-11-15 13:06:07 UTC
Created attachment 5444 [details]
Trace.log

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

Supplemental Info:
I couldn't reproduce this issue locally. 
Tracelogs, mtbserver.log from user is attached along with this bug report


Test Env:
Xamarin.iOS for VS 1.8.365.msi
Comment 1 GouriKumari 2013-11-15 13:06:31 UTC
Created attachment 5445 [details]
mtbserver.log
Comment 2 Vinicius Jarina 2013-11-22 16:41:11 UTC
This seems related to a Network issue.

https://gist.github.com/viniciusjarina/58289b09f40ae996cfb7

à System.Net.Dns.GetAddrInfo(String name)
   à System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
   à System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
   à MonoTouch.Tools.Utilities.Utils.<>c__DisplayClass6.<FastDnsResolve>b__4()
Comment 3 Alan McGovern 2013-11-25 11:18:44 UTC
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.
Comment 4 Dominique Louis 2013-11-26 09:50:40 UTC
@Gouri can you confirm Alan's diagnosis re the 429 error?
Comment 5 Alan McGovern 2013-11-26 10:51:20 UTC
http error 429 is the same as bug #16184 and the diagnosis there was clocks out of sync.
Comment 6 GouriKumari 2013-11-26 12:06:57 UTC
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.
Comment 7 Dominique Louis 2013-12-03 05:35:58 UTC
@GouriKumari Any updates from the user?
Comment 8 GouriKumari 2013-12-04 12:00:54 UTC
I have updated the deskcase and forum post related to this bug. However still hasn't got a reply from the user. 

DeskCase:
https://xamarin.desk.com/agent/case/51873
Comment 9 PJ 2013-12-04 12:03:36 UTC
Thanks Gouri.  Given the error code we can assume this was the clock skew issue, and RESOLVE as NORESPONSE (from the desk case).