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.
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.
If the connection of the server done properly, the timed out error should not appear.
Windows 7 and 8
Regression: Not a Regression. This issue also exists with Stable MTVS 1.0.897
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?
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.
We do need to figure out some sort of solution, I'll add it to the agenda for discussion after evolve.
We should make the web request timeout infinite.
Apparently we extended this recently to 10 minutes, can we jut make this infinite guys?
Apparently Jose was already looking into this issue.
I will assign it to him, in grendel's absence.
Today we have checked this issue with following builds :
We have tried to reproduce this issue many times but unable to get time out error while connection is strong.
Hence closing this issue.