Troubleshooting problems with ARCore API authorization

Select platform:

Keyless doesn't work (ERROR_NOT_AUTHORIZED)

When communication with the ARCore API server throws ERROR_NOT_AUTHORIZED, ensure that your application contains the library:

  1. Build your app, and check the resulting artifact with the APK Analyzer. Ensure that the built application binary includes the package, and that its contents are not renamed or minified.
    • If it is not present, follow Include required libraries and ensure the library is included and that the minification settings are correct.
  2. Show the security information present in the failing target artifact using the keytool utility:

    AAB artifact

    keytool -printcert -jarfile artifact.aab

    APK artifact

    keytool -printcert -jarfile artifact.apk
  3. Ensure the SHA-1 certificate fingerprint matches the credentials used in your project's OAuth 2.0 client ID.

  4. Ensure that you have enabled the ARCore API for the correct project in Google Cloud.

Keyless authorization is successful in some build types (e.g. Debug) but not in others

If keyless authorization succeeds in certain builds but not in others, ensure that the fingerprint present in the failing artifact matches the fingerprint listed in the Google Cloud Console. See Keyless authorization doesn't work and follow steps to verify that the signing key fingerprint for that artifact matches the fingerprint listed in Google Cloud.

Keyless authorization does not work when using Play App Signing

If keyless authorization works on your local builds, but not after uploading to the Google Play Store when Play App Signing is enabled, ensure that the SHA-1 certificate fingerprint registered in your project's credentials match the fingerprint Google uses to sign your app:

For more information, see Play App Signing.

API Key authentication is not working

If API Key authorization is not working, follow these steps:

  • Ensure that you have enabled the ARCore API for the correct project in Google Cloud.
  • If you have any API Key restrictions enabled, temporarily disable them.
  • Ensure that the API Key listed in your project's Credentials exactly matches the API Key used by your app, with no spaces or any other characters.