CLGeocoder returns unpredictable results

Originator:steven.baranski
Number:rdar://12892376 Date Originated:12/17/2012
Status:Closed Resolved:Apple claims that it behaves as intended.
Product:iPhone SDK Product Version:6.0.1
Classification:Other Bug Reproducible:Always
 
Summary:

CLGeocoder returns unpredictable results.

Steps to Reproduce:

1. Download the Apple Sample Code project named GeocoderDemo and run it - either in the iOS Simulator with a fabricated location or on-device.

2. Enter a location prefix (e.g., "San").

3. Tap "Geocode String" and observe the result(s).

Expected Results:

I would have expected either of the following to occur:
 (a) review multiple candidate results (e.g., San Antonio, San Diego, San Jose)
 (b) view the single closest result to my current location (e.g., San Antonio)

Specifying a Hint Region within said app does not appear to help.

Actual Results:

Returned "San" in the country of Mali. This might be an exact match for the unbounded search, but it's also returned when a hint region of 100.0 km is specified.

Regression:

(None)

Notes:

In fairness, the completion block -
typedef void (^CLGeocodeCompletionHandler)(NSArray *placemark, NSError *error);
- for both 
geocodeAddressString:completionHandler:
and
geocodeAddressString:inRegion:completionHandler:
states that "For most geocoding requests, this array should contain only one entry."

It seems logical that the single result might be closest to the user's current location, or at least to that of the specified hint region. That does not appear to be the case.

This was initiated via DTS Incident #244549677.

Thanks!

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!