Android - Handle errors

Efficiently manage errors in Android development using Adapty SDK's AdaptyError, ensuring comprehensive troubleshooting capabilities

Every error is returned by the SDK is AdaptyError.

UNKNOWN0This error indicates that an unknown or unexpected error occurred.
USER_CANCELED2This error indicates that the user canceled a payment request.
ITEM_UNAVAILABLE5This error mostly happens at the testing stage. It may mean that the products are absent from production or that the user does not belong to the Testers group in Google Play.
ADAPTY_NOT_INITIALIZED20You need to properly configure Adapty SDK by Adapty.activate method.
PRODUCT_NOT_FOUND22This error indicates that the product requested for purchase is not available in the store.
INVALID_JSON23The local fallback paywall JSON is not valid.
Fix your default English paywall, after that replace invalid local paywalls. Refer to the Customize paywall with remote config topic for details on how to fix a paywall and to the Define local fallback paywalls for details on how to replace the local paywalls.
24The original subscription that needs to be replaced is not found in active subscriptions.
PENDING_PURCHASE25This error indicates that the purchase state is pending rather than purchased. Refer to the Handling pending transactions page in the Android Developer docs for details.
BILLING_SERVICE_TIMEOUT97This error indicates that the request has reached the maximum timeout before Google Play can respond. This could be caused, for example, by a delay in the execution of the action requested by the Play Billing Library call.
FEATURE_NOT_SUPPORTED98The requested feature is not supported by the Play Store on the current device.
BILLING_SERVICE_DISCONNECTED99This error indicates that the client app’s connection to the Google Play Store service via the BillingClient has been severed.
BILLING_SERVICE_UNAVAILABLE102This error indicates the Google Play Billing service is currently unavailable. In most cases, this means there is a network connection issue anywhere between the client device and Google Play Billing services.
BILLING_UNAVAILABLE103This error indicates that a user billing error occurred during the purchase process. Examples of when this can occur include:

1. The Play Store app on the user's device is out of date.
2. The user is in an unsupported country.
3. The user is an enterprise user, and their enterprise admin has disabled users from making purchases.
4. Google Play is unable to charge the user’s payment method. For example, the user's credit card might have expired.
DEVELOPER_ERROR105This error indicates you're improperly using an API.
BILLING_ERROR106This error indicates an internal problem with Google Play itself.
ITEM_ALREADY_OWNED107The product has already been purchased.
ITEM_NOT_OWNED108This error indicates that the requested action on the item failed since it is not owned by the user.
BILLING_NETWORK_ERROR112This error indicates that there was a problem with the network connection between the device and Play systems.
NO_PRODUCT_IDS_FOUND1000This error indicates that none of the products in the paywall is available in the store.
If you are encountering this error, please follow the steps below to resolve it:

1. Check if all the products have been added to Adapty Dashboard.
2. Ensure that the Bundle ID of your app matches the one from the Apple Connect.
3. Verify that the product identifiers from the app stores match with the ones you have added to the Dashboard. Please note that the identifiers should not contain Bundle ID, unless it is already included in the store.
4. Confirm that the app paid status is active in your Apple tax settings. Ensure that your tax information is up-to-date and your certificates are valid.
5. Check if a bank account is attached to the app, so it can be eligible for monetization.
6. Check if the products are available in all regions.

Also, ensure that your products are in “Ready to Submit” state.
NO_PURCHASES_TO_RESTORE1004This error indicates that Google Play did not find the purchase to restore.
AUTHENTICATION_ERROR2002You need to properly configure Adapty SDK by Adapty.activate method.
BAD_REQUEST2003Bad request.
SERVER_ERROR2004Server error.
REQUEST_FAILED2005This error indicates a network issue that cannot be properly defined.
DECODING_FAILED2006We could not decode the response.
ANALYTICS_DISABLED3000We can't handle analytics events, since you've opted it out.
WRONG_PARAMETER3001This error indicates that some of your parameters are not correct: blank when it cannot be blank or wrong type, etc.

What’s Next