Handle errors in Android SDK

Every error is returned by the SDK is AdaptyError.

important

If these solutions don't resolve your issue, see Other issues for steps to take before contacting support to help us assist you more efficiently.

Error	Solution
UNKNOWN	This error indicates that an unknown or unexpected error occurred.
ITEM_UNAVAILABLE	This 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_INITIALIZED	The Adapty SDK is not activated. You need to properly configure Adapty SDK using the Adapty.activate method.
PRODUCT_NOT_FOUND	This error indicates that the product requested for purchase is not available in the store.
INVALID_JSON	The 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.
CURRENT_SUBSCRIPTION_TO_UPDATE _NOT_FOUND_IN_HISTORY	The original subscription that needs to be replaced is not found in active subscriptions.
BILLING_SERVICE_TIMEOUT	This 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_SUPPORTED	The requested feature is not supported by the Play Store on the current device.
BILLING_SERVICE_DISCONNECTED	This error indicates that the client app’s connection to the Google Play Store service via the BillingClient has been severed.
BILLING_SERVICE_UNAVAILABLE	This 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_UNAVAILABLE	This error indicates a billing issue occurred during the purchase process. Possible reasons include: 1. The Play Store app on the user's device is missing or outdated. 2. The user is in an unsupported country. 3. The user is part of an enterprise account where the admin has disabled purchases. 4. Google Play couldn't charge the user's payment method (e.g., an expired credit card). 5. The user is not logged into the Play Store app.
DEVELOPER_ERROR	This error indicates you're improperly using an API.
BILLING_ERROR	This error indicates an internal problem with Google Play itself.
ITEM_ALREADY_OWNED	The product has already been purchased.
ITEM_NOT_OWNED	This error indicates that the requested action on the item failed since it is not owned by the user.
BILLING_NETWORK_ERROR	This error indicates that there was a problem with the network connection between the device and Play systems.
NO_PRODUCT_IDS_FOUND	This 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: Check if all the products have been added to Adapty Dashboard. Ensure that the Package name of your app matches the one from the Google Play Console. Verify that the product identifiers from the app stores match those you have added to the Dashboard. Please note that the identifiers should not contain Bundle ID, unless it is already included in the store. Confirm that the app paid status is Active in your Google tax settings. Ensure that your tax information is up-to-date and your certificates are valid. Check if a bank account is attached to the app, so it can be eligible for monetization. Check if the products are available in your region. Ensure your app is in one of the testing tracks. The Internal testing track is the easiest option since it doesn’t require a review and keeps the app hidden from customers.
NO_PURCHASES_TO_RESTORE	This error indicates that Google Play did not find the purchase to restore.
AUTHENTICATION_ERROR	You need to properly configure Adapty SDK by Adapty.activate method.
BAD_REQUEST	Bad request. Ensure you've completed all the steps required to integrate with Google Play.
SERVER_ERROR	Server error.
REQUEST_FAILED	This error indicates a network issue that cannot be properly defined.
DECODING_FAILED	We could not decode the response. Review your code and ensure that you the parameters you send are valid. For example, this error can indicate that you're using an invalid API key.
ANALYTICS_DISABLED	We can't handle analytics events, since you've opted it out.
WRONG_PARAMETER	This error indicates that some of your parameters are not correct: blank when it cannot be blank or wrong type, etc.

Other issues

If you haven't found a solution yet, the next steps can be:

• Upgrading the SDK to the latest version: We always recommend upgrading to the latest SDK versions since they are more stable and include fixes for known issues.
• Contact the support team via [email protected] or via the chat: If you are not ready to upgrade the SDK or it didn't help, contact our support team. Note that your issue will be resolved faster if you enable verbose logging and share logs with the team. You can also attach relevant code snippets.