xCode9.2集成GoogleMaps 2.6无法获取逆地理编码结果求助

Let's break down the most likely causes and fixes for your reverse geocoding problem—since your web API works but the iOS SDK doesn't, we can focus on client-side configuration and code first:

1. First, Verify Your REVERSED_CLIENT_ID #

This is the most common pitfall for iOS Google Maps SDK issues:

• Head to your Google Cloud Console, locate the iOS OAuth 2.0 Client ID for your project (this is different from your API Key!).
• The original client ID follows this format: 1234567890-abcdefghijklmnop.apps.googleusercontent.com
• Your reversed client ID needs to flip the domain structure: com.googleusercontent.apps.1234567890-abcdefghijklmnop
• Double-check your Info.plist entry for GMSReverseClientID—make sure it's an exact match, no extra spaces, typos, or capitalization errors. Even one wrong character will block SDK authentication.

2. Validate Your API Key Configuration #

Even if the web API works, the iOS SDK has specific requirements:

• Ensure the Geocoding API is enabled in your Cloud Console (it’s a separate API from the Maps SDK for iOS—don’t assume enabling Maps covers it).
• Check API Key restrictions: If you set iOS Bundle ID restrictions, confirm it matches your app’s Bundle ID exactly (capitalization matters! com.MyApp ≠ com.myapp).
• Verify you haven’t hit the Geocoding API quota limit—check the "Usage" tab in Cloud Console for any quota-related errors.

3. Audit Your Reverse Geocoding Code #

Make sure you’re handling callbacks correctly and not ignoring critical error details:
Here’s a minimal working example to compare against:

// Objective-C
GMSGeocoder *geocoder = [[GMSGeocoder alloc] init];
CLLocationCoordinate2D testCoord = CLLocationCoordinate2DMake(37.7749, -122.4194); // SF downtown
[geocoder reverseGeocodeCoordinate:testCoord completionHandler:^(GMSReverseGeocodeResponse *response, NSError *error) {
    // Always check for errors first!
    if (error) {
        NSLog(@"Reverse geocode failed: %@", error.localizedDescription);
        return;
    }
    
    if (response.results.count == 0) {
        NSLog(@"No address results found");
    } else {
        GMSAddress *firstResult = response.results.firstObject;
        NSLog(@"Found address: %@, %@", firstResult.locality, firstResult.country);
    }
}];

• The callback runs on a background thread—if you need to update UI, wrap that code in dispatch_async(dispatch_get_main_queue(), ^{ ... }).
• Never skip logging the error object! It will tell you exactly what’s wrong (invalid key, auth failure, network issue, etc.).

4. Dig Into Xcode Console Logs #

You mentioned seeing repeated prompts—those logs are critical for debugging. Filter the console for GoogleMaps or Geocoding to find detailed error messages:

• If you see Invalid reverse client ID, circle back to step 1 to fix your ID configuration.
• If you see API key not valid, check your API Key’s enabled status or bundle ID restrictions.
• If you see Network error, verify your device/simulator has proper internet access (note: Google services are blocked in mainland China, so you’ll need a workaround there).

5. Rule Out Version-Specific Bugs #

You tried 2.2, 2.5, 2.6—none of these versions have known widespread reverse geocoding breaks. Since the web API works, this is almost certainly a client-side configuration issue, not a SDK bug.

Start with the REVERSED_CLIENT_ID and API Key checks first—those are the most frequent culprits here. If you share the exact error messages from your console, we can narrow it down even further!

内容的提问来源于stack exchange，提问作者czane