Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases
Develop
Test
Publish
Monetize
Engage users
Device specifications
Resources
Skip to main content
Here you can find the A3L Authentication API reference, a list of scopes that A3L Authentication supports, troubleshooting information, and frequently asked questions.

A3L Authentication API reference

For details on the classes and methods contained in A3L Authentication, see the complete A3L Authentication API Reference.

Scopes supported by A3L Authentication

In A3L Authentication, a user can grant access to the scopes listed in the following table.
Scopes supported by A3L Authentication
ConstantDescription and Value
EMAILOAuth 2.0 scope for accessing a user’s Google account email address:
email
PROFILEOAuth 2.0 scope for viewing a user’s basic profile information:
profile
OPEN_IDOAuth 2.0 scope for accessing OpenID for the profile:
openid

Troubleshooting

This section contains troubleshooting information to help you identify, isolate, and resolve issues you might encounter when integrating A3L Authentication.

Build fails for apps with minimum Android API level 20 or lower

If your app must support API level 20 or lower and multidex isn’t enabled, it’s possible your build could fail. To solve this issue, enable multidex for your app by following the guidelines in the Android developer documentation to Enable multidex.

Google Sign-In pop-up doesn’t show after clicking Sign In

Check if you have the correct configuration in your API Console and in A3L Authentication. If you’ve provided the client ID, check the SHA1 and package name that you provided to create the client ID and make sure they match. If they don’t match, Google doesn’t recognize the app and the pop-up doesn’t appear. Make sure to modify the credentials to have correct SHA1 and package name. For details about how to configure your app, see Configure Google API Console.

After authentication, Custom Tab redirects to Google homepage

If after authentication, the user is redirected to the Google homepage and not back to the app, you might have misconfigured your manifest placeholder. Provide the Android client ID prefix in the manifest placeholder inside the build.gradle file. For instructions, see Add A3L Authentication SDK to your project.

Unable to initialize A3L Authentication

If A3L Authentication initialization fails and you receive “Internal Error APIException”, there might be a problem with your A3L Authentication SDK installation. Replace your A3L Authentication AAR with the latest version available.

FAQ

The following are frequently asked questions (FAQ) about A3L Authentication.
Last modified on February 11, 2026