Open Radar

 
Summary:
When submitting a forward geocoding request for "new york", the server responds with a 500 error:

/SourceCache/ProtocolBuffer/ProtocolBuffer-187.4/Runtime/PBRequester.m:825 server (https://gsp-ssl.ls.apple.com/fwdgeo.arpc) returned error: 500

Started 5/22/14 as far as I can tell.  Is it anything related to heartbleed requiring iOS devices to be updated with new certificates?

Steps to Reproduce:
Create a simple app with a geocoding request:

CLGeocoder *geocoder = [[CLGeocoder alloc] init];

[geocoder geocodeAddressString:@"New York"
     completionHandler:^(NSArray* placemarks, NSError* error){
         CLPlacemark *geoResult = [placemarks objectAtIndex:0];
         if(error != nil) {
             NSLog(@"%@",[error description]);
         } else {
             //do something
         }
}];


Expected Results:
Expect to get at least one CLPlacemark in the NSArray of placemarks.

Actual Results:
Message appears in console:
/SourceCache/ProtocolBuffer/ProtocolBuffer-187.4/Runtime/PBRequester.m:825 server (https://gsp-ssl.ls.apple.com/fwdgeo.arpc) returned error: 500

NSLog the error gives:
2014-05-23 15:35:11.262 Run10Feed10[331:60b] Error Domain=kCLErrorDomain Code=2 "The operation couldn’t be completed. (kCLErrorDomain error 2.)"



Version:
iPhone 5S is 11D201 - seems independent of device or iOS version/build

Notes:
Apple developer forums and stackoverflow both showing consistent error reports in the US:
https://devforums.apple.com/message/968027#968027
http://stackoverflow.com/questions/23819466/error-return-address-clgeocoder/23836835#23836835

Configuration:
iPhone 4 (7.1), 4S (7.0.4), 5S (7.1.1) and iPad Mini (7.1.1) on wifi and using Verizon LTE

Attachments: