Troubleshoot Android SDK configuration load failures

Problem description

How do I resolve configuration load failures?

FAQ

Check the debug log by setting the log level to `debug` or `verbose`.

Security image issues

Search for the error code:

  - ErrorCode = 607: There is a problem with the image file. This usually happens when the APK signature used to get the image file does not match the current application's APK signature. Regenerate the image using the current application's APK. When you upload the image, make sure the appkey of the backend application matches the appkey used in the application.
  - ErrorCode = 608: The image file was not found. Make sure the image file is in the res\drawable folder. In an Android environment, this can happen if resource optimization reduces the file size to 0. Check the image in the APK. This is often caused using shrinkResource in Gradle.
  - ErrorCode = 611: The key in the parameter cannot be found in the image file. Confirm that the image file contains this key. 

utdid conflict issues

Most software development kits (SDKs) from Alibaba depend on utdid. To prevent conflicts, keep the utdid version included with our SDK and delete all other versions.

allowBackup issues

Set `allowBackup` to `false` in the AndroidManifest file.

Security permission prompt issues

Because each app has a unique style, the styling for the security permission prompt cannot be standardized. You must add the prompt yourself.

Parameter error during feedback submission

Set `minifyEnabled` to `false` in your Gradle file.