Bug 11517 - [VS 2010/12] 'Time out' error appears after deployment, even if connection is strong.
Summary: [VS 2010/12] 'Time out' error appears after deployment, even if connection is...
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.1.x
Hardware: PC Windows
: Normal normal
Target Milestone: 1.6.x (connection)
Assignee: Jose Miguel Torres
URL:
Depends on:
Blocks:
 
Reported: 2013-04-02 07:35 UTC by narayanp
Modified: 2013-11-15 09:01 UTC (History)
8 users (show)

Tags: papercut, error improvement
Is this bug a regression?: ---
Last known good build:

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:
VERIFIED FIXED

Description narayanp 2013-04-02 07:35:16 UTC
On running any iOS application through VS, it deploys successfully but after some time (5-7 minutes) the time out error appears: 'Xamarion.iOS Error' popup appears with message 'The request was aborted. The operation has timed out'.

Note: It is an intermittent issue and the frequency of occurrence 2 out of 10.

Expected result:
If the connection of the server done properly, the timed out error should not appear.

Environment info:
Windows 7 and 8
VS 2010/12
MTVS 1.1.197
MT 6.2.2.7(Server)

Regression: Not a Regression. This issue also exists with Stable MTVS 1.0.897
Comment 1 PJ 2013-04-02 11:48:55 UTC
It's always hard to determine the source of the network flakiness, but I also see the timeout dialog way too much.

I think we might have some sort of problem with the timeout logic, or at least we could more reliably reconnect when a network interruption occurs?
Comment 2 Marek Habersack 2013-04-03 05:35:01 UTC
We can make the timeouts on web requests shorter, certainly, and then retry the connection but that creates a new set of problems. Namely, since the timeout occurred we have no way of knowing (currently) what was the completion status of the command that timed out. Fixing this requires making the requests stateful - certainly not a quick fix.
Comment 3 PJ 2013-04-04 15:09:28 UTC
We do need to figure out some sort of solution, I'll add it to the agenda for discussion after evolve.
Comment 5 Miguel de Icaza [MSFT] 2013-05-01 12:34:15 UTC
We should make the web request timeout infinite.

Apparently we extended this recently to 10 minutes, can we jut make this infinite guys?
Comment 6 Dominique Louis 2013-05-01 14:09:58 UTC
Apparently Jose was already looking into this issue.

I will assign it to him, in grendel's absence.

D.
Comment 12 Akhilesh kumar 2013-11-15 09:01:24 UTC
Today we have checked this issue with following builds :

VS 2013
MTVS 1.8.365

We have tried to reproduce this issue many times but unable to get time out error while connection is strong.

Hence closing this issue.