![]() ![]() The newly signed APK doesn’t get flagged as suspicious google play protect. Solution 2: I created a new Key Store, setting it to 50 years and fill up all the available fields. I suspect this is the default Play Protect behaviour: Play Protect will popup warning upon first installtion of suspicious APK, after which it will block the installation without further warning. ![]() Solution 1: If I disabled Play Protect (Setting -> Google -> Security -> Google Play Protect -> Disable “Scan device for security threats”), the installation go through without problem. The same happend (“App not installed”) if I uninstalled the app and try to install again. I suspect it is related to Google Play Protect. I check the google source and found INSTALL_FAILED_VERIFICATION_FAILURE = -22. If I didn’t click “Install Anyway” and try to install the apk again, it will show “App not installed” (it might or might now show error code -22, depending on Android version). I click “Install Anyway” and the installation proceed as usual. ![]() I created a Key Store for 25 years and only fill up Country Code, the Released Build + Signed APK (Both V1 and V2 Signature Versions) trigger Play Protect warning on first install. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |