Bug 5643 - Reverse geodecoding sometimes fails with the error message: The operation couldn't be completed. (NSURLErrorDomain error -1011.)
Summary: Reverse geodecoding sometimes fails with the error message: The operation cou...
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 5.2
Hardware: Other Other
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-06-14 02:01 UTC by dj_technohead
Modified: 2012-06-20 07:40 UTC (History)
2 users (show)

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 or GitHub 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:

Description dj_technohead 2012-06-14 02:01:42 UTC

Comment 1 dj_technohead 2012-06-14 02:02:53 UTC
Seeing this in the console just after starting the reverse geodecode operation:
/SourceCache/ProtocolBuffer/ProtocolBuffer-92/Runtime/PBRequester.m:687 server returned error: 503
6/13/2012 10:55:53 PM::The operation couldn?t be completed. (NSURLErrorDomain error -1011.)::
Comment 2 dj_technohead 2012-06-14 15:26:23 UTC
If this is an intermittent error from Google Maps, how can I trap this error so that I can handle it better?
Comment 3 Rolf Bjarne Kvinge [MSFT] 2012-06-20 07:40:22 UTC
I believe this happens when you hit their server too often.

In any case it's nothing MonoTouch can do about it (and as far as I can see the only place you actually see this is in the logs, there is no way to catch or handle this condition).