Troubleshooting your Android App Protection

This is most likely because the app hasn't been signed correctly.

See our guide to signing a protected Android App.

If you are still seeing problems, please contact our support team for help.

This is most likely because the app was locked to a different signing key than the one used to sign the app.

See our guide to signing a protected Android App.

If you are still seeing problems, please contact our support team for help.

First, confirm that the problem is not present in an unprotected application. If it only occurs in a protected application, you should identify the code that is now exhibiting the problem (for a crash, a good place to start is the stack trace within ADB's logcat output).

If your usage tier includes support, you can flag the build as problematic using the "Report a Problem" link on the Protection Status page and our support team will investigate for you.

If the upload fails with an error message about the app not being supported for protection, check that your app conforms to the prerequisites described in Preparing your Android App.

If the app fails before the upload progress indicator reaches 100%, check that your network is stable and that any anti-virus installed on your computer isn't blocking the upload.

For other issues, contact our support team for help.

This is likely caused by debuggable defined as true in the application gradle file. It must be set to false for the uploaded APK.

Only release build variants can be protected. Rebuild your application in release mode and upload again. For details how to change the build variant in Android studio, refer to the Android developers' guide Build and run your app.

You can verify the status of debuggable in your packaged app via the following steps:

Extract the manifest using

unzip -p {APK_NAME}.apk AndroidManifest.xml > AndroidManifest.xml
where {APK_NAME}.apk is the file name of the apk to be uploaded. Check the debuggable setting in the extracted AndroidManifest.xml file.