After applying Doverunner AppSecurity to an AAB/APK, your app may run normally when launched directly on a smartphone. However, it might not function properly after being uploaded to the Google Play Store.
If this issue occurs, You have two methods to resolve this issue.
Disable Automatic Protection in Google Play Console
Disable File Integrity Check when protecting app with Doverunner.
1. Disable Automatic Protection in Google Play Console
check the Automatic Protection settings in the Play Store Console. Navigate to your app > Protected with Play, then check Automatic Protection status. If this option is enabled, disable it before re-uploading and testing your app on the Play Store.
When an app is uploaded to the console with Automatic Protection enabled, the Play Store may insert additional security modules to enhance app protection. However, if AppSealing is already applied, any additional modifications to the app may be detected as tampering, causing AppSealing to forcibly terminate the app.
As of June 2026, Doverunner AppSecurity does not support compatibility with the Automatic Protection feature. Therefore, it is essential to disable Automatic Protection before uploading your app to the Play Store.
Please check the below screenshot. Automatic protection must be disabled. and upload new app after turn off this.
2. Disable File Integrity Check when protecting app with Doverunner
This feature is available from AppSecurity version 3.2.0.0
Because Google Automatic Protection change the app`s code and configurations, Doverunner will recognize it as File Integrity check failure. ( Unofficial app detected popup )
To avoid this detection, you can disable File Integrity in Doverunner console. You can Disable File Integrity Check, when you need to use GooglePlay Automatic protection.
But also recommended to enable Signing Certificate Identity Checks, to not miss the app`s integrity level. You can find the instruction for this feature at below page.