Appstore Billing Compatibility SDK Troubleshooting
This page contains troubleshooting guidance for issues that could occur while integrating with the Appstore Billing Compatibility SDK.
- Duplicate class exception
- AUTH_TOKEN_VERIFICATION_FAILURE
- Unresolved import statements
- Related topics
Duplicate class exception
If your app has a dependency on both the Appstore SDK and the Appstore Billing Compatibility SDK, a duplicate class exception can occur when integrating with the Appstore Billing Compatibility SDK.
Duplicate class com.amazon.a.a found in modules
jetified-amazon-appstore-sdk-3.0.3 (com.amazon.device:amazon-appstore-sdk:3.0.3)
and
jetified-appstore-billing-compatibility-4.0 (appstore-billing-compatibility-4.1.0.jar)
Your app can use either the Appstore Billing Compatibility SDK or the Appstore SDK, but not both. To use the Appstore Billing Compatibility SDK, you must remove the Appstore SDK dependency from your app.
AUTH_TOKEN_VERIFICATION_FAILURE
When testing your app, an AUTH_TOKEN_VERIFICATION_FAILURE
error can occur if there is a mismatch between the public key allocated for your app in the Developer Console and the public key your app uses. Make sure that you use the unique public key that the Developer Console provides for your app. If you have multiple apps in your account, each app has a different public key.
AbstractCommandTask: Exception occurred while processing task:
com.amazon.a.a.n.a.a.a: AUTH_TOKEN_VERIFICATION_FAILURE: null: null
For details on how to correct this error, follow the instructions in AUTH_TOKEN_VERIFICATION_FAILURE.
Unresolved import statements
After adding the Appstore Billing Compatibility SDK to your app, you must update the import statement from the com.android.billingclient.api
prefix to the com.amazon.device.iap.billingclient.api
prefix. If after updating your code, unresolved import statements remain, you might be using unsupported fields.
The current version of the Appstore Billing Compatibility SDK doesn't support the following fields:
If your code has a dependency on these fields, remove the corresponding dependencies. You can remove the functionality supported by these fields and gracefully handle the exception.
Related topics
- Appstore Billing Compatibility SDK—overview and integration guide
- Implement the Google Play Billing Interface
- Appstore Billing Compatibility Subscriptions
- Appstore Billing Compatibility SDK Best Practices
- Appstore Billing Compatibility API Reference
Last updated: Oct 14, 2024