How to deal with MKReverseGeocoder / PBHTTPStatusCode=503 errors in iOS 4.3?

Question

Since iOS 4.3 (GM Seed 10M2518) I'm getting crashes when using MKReverseGeocoder. reverseGeocoder:didFailWithError: gets called with an error like this quite often:

Error Domain=NSURLErrorDomain Code=-1011 "The operation couldn’t be completed. (NSURLErrorDomain error -1011.)" UserInfo=0x339900 {PBHTTPStatusCode=503}

The app tends to crash at these moments. This hasn't been the case in previous versions of iOS.

Any ideas what happened?

score 5 · Accepted Answer · answered Mar 14 '11 at 14:01

5

Make sure you don't release the reverse geocoder prematurely on failure:

Changing [_reverseGeocoder release] to [_reverseGeocode autorelease] in -(void)reverseGeocoder:(MKReverseGeocoder *)geocoder didFailWithError:(NSError *)error fixed the problem for me.

answered Mar 14 '11 at 14:01

utopalex

1,324
10
9

i m not releasing geocoder object but still didFailWithError .can you explain reason ..http://stackoverflow.com/questions/7443252/at-first-time-mkreversegeocoder-didfailwitherrorerror-domain-nsurlerrordomain-c – Srinivas Sep 16 '11 at 10:58
same here.. Any solution?? Thanks – Frade Feb 01 '12 at 16:49
You must be calling it a lot too many times http://stackoverflow.com/questions/2941495/mkreversegeocoder-server-returned-error-503 – Ashish Awaghad Mar 02 '12 at 08:34

score 4 · Answer 2 · answered Jul 21 '11 at 15:10

Google doesn't allow a single device to retrieve its location more than once within 60 sec, hence working with another method (http request instead, JSON needed) when (MKReverseGeocoder *)geocoder didFailWithError.

It works for me on 4.3.3 (3GS) and tested for 30-40 times retrieving user's location consecutively without a crash, hope it helps!

- (void) retrieveCurrentLoc {
self.geoCoder =
[[[MKReverseGeocoder alloc] initWithCoordinate:newLocation.coordinate] autorelease];
    geoCoder.delegate = self;

    [geoCoder start];
}

- (void)reverseGeocoder:(MKReverseGeocoder *)geocoder didFailWithError:(NSError *)error{

NSString *fetchURL = [NSString stringWithFormat:@"http://maps.google.com/maps/geo?    q=%@,%@&amp;output=json&amp;sensor=true", [NSString     stringWithFormat:@"%f",mapView.userLocation.location.coordinate.latitude], [NSString      stringWithFormat:@"%f",mapView.userLocation.location.coordinate.longitude]];
    NSURL *url = [NSURL URLWithString:fetchURL];
    NSString *htmlData = [NSString stringWithContentsOfURL:url];

SBJsonParser *parser = [[SBJsonParser alloc] init];
NSDictionary *json = [parser objectWithString:htmlData error:nil];
NSArray *placemark = [json objectForKey:@"Placemark"];
if ([[[[[placemark objectAtIndex:0]     objectForKey:@"AddressDetails"]objectForKey:@"Country"]objectForKey:@"Thoroughfare"]objectFor  Key:@"ThoroughfareName"] != NULL){
    currentAddress = [[[[[placemark objectAtIndex:0]     objectForKey:@"AddressDetails"]objectForKey:@"Country"]objectForKey:@"Thoroughfare"]objectFor  Key:@"ThoroughfareName"];}
else {
    currentAddress = [[placemark objectAtIndex:0] objectForKey:@"address"];
    }
}

So you fallback to doing an explicit JSON request if the packaged MKReverseGeocoded didn't work. Strange solution isn't it? The code would be more compact if you just did the explicit request in the first place. — Harry Wood, Jan 10 '12 at 18:35

score 2 · Answer 3 · answered Mar 11 '11 at 11:46

Same problem here, we checked various solutions and didn't work. The 503 response code is handled differently by the previous OS, you can easily notice that by sniffing the iPhone traffic.

Applications that rely on MKReverseGeocoder (like Gowalla) will make some pressure against Apple ... so I would expect a 4.3.1 hotfix coming these days. Or Google to change their SLA with Apple requests.

score 1 · Answer 4 · answered Apr 07 '11 at 09:36

Following on from zippo77's answer, I found best results when setting the MKReverseGeocoder delegate to nil first in -(void)reverseGeocoder:(MKReverseGeocoder *)geocoder didFailWithError:(NSError *)error

_reverseGeocoder.delegate = nil;
[_reverseGeocoder autorelease];

score 1 · Answer 5 · answered Apr 28 '11 at 12:37

I had the same issue, even though my MKReverseGeocoder code followed one of the Apple examples (MKReverseGeocoder as a global autorelease variable). Also the issue appeared only on iOS 4.3 (4.0 was running no problem).

What solved the problem for me was removing the autorelease part and releasing the MKReverseGeocoder only in dealoc of the view.

score 1 · Answer 6 · answered Aug 09 '11 at 10:37

1

Probably you are stoping location manager before geo coder will find placemark. Do it in didFindPlacemark or for error

answered Aug 09 '11 at 10:37

SergD

11
1

How to deal with MKReverseGeocoder / PBHTTPStatusCode=503 errors in iOS 4.3?

6 Answers6

Linked