PLACES API_ACCESS NOT CONFIGURED错误求助：已启用API仍触发该状态码

Hey there, let's work through this frustrating error—even with the Places API enabled, that PLACES API_ACCESS NOT CONFIGURED message can pop up for a few easy-to-miss reasons in the old Google API Console. Here's what to check step by step:

• Double-check your API key's application restrictions
  The old console is notoriously finicky with key restrictions. Head to your API key settings and verify:

  • For Android apps: The package name and SHA-1 fingerprint exactly match your app's build (debug and release fingerprints are different—don't mix them up!).
  • For iOS apps: The Bundle ID is correctly entered.
  • If you're using a server-side key: IP restrictions aren't blocking your server's outgoing requests.
    Even a tiny typo here can trigger the access error.

• Ensure you've enabled the correct Places API variant
  This is a super common gotcha! The "Places API" (Web Service) and "Places SDK for Android/iOS" are separate services in the old console. If you're building a mobile app, enabling just the web service version won't work—you need to enable the platform-specific Places SDK instead. Go back to the API library and confirm the right one is toggled on.

• Verify your API key is linked to the correct project
  If you have multiple projects in the old console, it's easy to generate a key in one project but enable the Places API in another. Check that the key you're using in your app belongs to the same project where you turned on the Places service.

• Wait for configuration propagation (or refresh)
  Google's API settings don't always take effect instantly, especially in the older console. Close the console tab, clear your browser cache, then wait 5-10 minutes before testing again. Sometimes the system just needs a minute to sync your changes.

• Check for mismatched API endpoints
  If you're making direct HTTP requests instead of using the official SDK, make sure you're hitting the right endpoint for your enabled API. For example, the mobile Places SDKs use internal endpoints, while the web service uses https://maps.googleapis.com/maps/api/place/...—mixing these can cause access denied errors even if the key is correct.

• Dig into detailed error logs
  Head to the Places API's "Monitoring" or "Logs" section in the old console. You'll find granular details about failed requests—like whether the key was invalid, restrictions were violated, or the API wasn't properly enabled for the project. This can cut straight to the root cause.

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