mohsen programmer
Member
I am a developer of an application that has been previously published on Google Play and other markets without any issues. Recently, Google Play removed my application from publication due to a surge in installation errors. According to Google, in recent days, 75% of users have encountered the install_failed_verification_failure error during installation.
Upon further investigation in the developer console, I noticed that previously less than 1% of users experienced this error, but this rate has drastically increased in recent days. Notably, there are no issues when installing the application on an A24 device (and my other test devices); the installation completes successfully.
The application was updated about a month ago. The new version is compiled with B4A version 13 and Android SDK 33, while previous versions were compiled with B4A version 12.80 and Android SDK 33.
Very importantly: I previously raised concerns about a potential issue with the application's signature in the B4X forum (https://www.b4x.com/android/forum/t...ystore-in-the-near-future.161537/#post-991093). Although I have signed other applications with the same key and have not encountered any issues so far, there is a possibility of a problem with the signature of this specific application.
My application's manifest:
Given the above explanations and the provided manifest, I kindly request guidance on the following matters:
Thank you for your time and assistance.
Upon further investigation in the developer console, I noticed that previously less than 1% of users experienced this error, but this rate has drastically increased in recent days. Notably, there are no issues when installing the application on an A24 device (and my other test devices); the installation completes successfully.
The application was updated about a month ago. The new version is compiled with B4A version 13 and Android SDK 33, while previous versions were compiled with B4A version 12.80 and Android SDK 33.
Very importantly: I previously raised concerns about a potential issue with the application's signature in the B4X forum (https://www.b4x.com/android/forum/t...ystore-in-the-near-future.161537/#post-991093). Although I have signed other applications with the same key and have not encountered any issues so far, there is a possibility of a problem with the signature of this specific application.
My application's manifest:
B4X:
AddManifestText(
<uses-sdk android:minSdkVersion="21" android:targetSdkVersion="34"/>
<supports-screens android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:anyDensity="true"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="moe.shizuku.manager.permission.API_V23" />
)
SetApplicationAttribute(android:icon, "@drawable/icon")
SetApplicationAttribute(android:label, "$LABEL$")
CreateResourceFromFile(Macro, Themes.DarkTheme)'
AddApplicationText(
<provider
android:name="rikka.shizuku.ShizukuProvider"
android:authorities="com.sbj.social.shizuku"
android:enabled="true"
android:exported="true"
android:multiprocess="false"
android:permission="android.permission.INTERACT_ACROSS_USERS_FULL" />
<meta-data
android:name="moe.shizuku.client.V3_SUPPORT"
android:value="true" />
)
SetApplicationAttribute(android:requestLegacyExternalStorage, true)
AddPermission(android.permission.READ_EXTERNAL_STORAGE)
AddPermission(android.permission.WRITE_EXTERNAL_STORAGE)
SetApplicationAttribute(android:requestLegacyExternalStorage,"true")
SetApplicationAttribute(android:usesCleartextTraffic, "true")
SetApplicationAttribute(android:largeHeap, "true")
SetActivityAttribute(activity_videos,
android:screenOrientation,
"landscape"
)
SetApplicationAttribute(android:icon, "@mipmap/ic_launcher")
CreateResource(mipmap-anydpi-v26, ic_launcher.xml,
<adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">
<background android:drawable="@mipmap/background"/>
<foreground android:drawable="@mipmap/foreground"/>
</adaptive-icon>)- What is the likely cause of the sudden and significant increase in the install_failed_verification_failure error?
- How can this error be resolved?
- Could the change in the B4A version from 12.80 to 13 contribute to this issue? (Despite the SDK remaining the same)
- Are there any specific settings in B4A or the publishing process that should be checked?
- Considering the previous discussion about the application's signature, could the problem be related to the signature type, even if other applications signed with the same key have been published without issues?
- Based on the provided manifest, are there any specific settings in the manifest that could cause this error?
Thank you for your time and assistance.