Install failed verification failure during Blueprint converge: switch app ABI to multi-arch

Android

If your app installation fails during Blueprint convergence with the error INSTALL_FAILED_VERIFICATION_FAILURE, Google Play Protect on your devices may be blocking the installation. This article explains how to resolve this issue by rebuilding your app with multi-architecture support.

Before you begin

This issue typically occurs when you deploy an app built for a single architecture (arm64-only). The solution requires rebuilding your app to support multiple architectures. If you're experiencing intermittent installation failures on a subset of your devices, this guide will help you resolve it.

How to resolve the installation failure

1. Rebuild your app with multi-architecture support. Configure your app build to include at minimum both arm64-v8a and armeabi-v7a architectures in your APK or App Bundle.
2. Upload the new build to Esper Console. Navigate to Apps → select your app → Upload New Version and upload the updated multi-architecture APK.
3. Update your Blueprint. Go to Blueprints → select the relevant Blueprint → Apps section → update the app version to the newly uploaded build.
4. Converge the Blueprint. Navigate to Devices & Groups → select the affected devices → Blueprint → Apply / Converge.
5. Upgrade your Esper Agent (recommended). Before or during the convergence, upgrade the Esper Agent to the latest available version on your affected devices via the Esper Console. Newer Agent versions include improvements for Google Play Protect interactions.
6. Verify the deployment. Check that the convergence status shows Compliant in the Esper Console for previously failing devices. Confirm that the app version displayed under the device's Apps tab matches your newly deployed build.

Alternative approach: Disable Play Protect on individual devices

If rebuilding your app is not feasible, you can manually disable Google Play Protect on individual devices. Note that this approach is not scalable for large fleets.

1. Enable Google Play Store on the device via Blueprint or Device Settings.
2. Open the Play Store app on the device → tap the profile icon → Play Protect → disable Scan apps with Play Protect.
3. Trigger a re-convergence from the Esper Console on that device.
4. Re-disable Play Store if your policy requires it after the convergence completes.

Gather diagnostic information if the issue persists

If the above steps don't resolve your installation failures, collect diagnostic information from a failing device:

• Navigate to Devices & Groups → select the device name → Actions → Request Bug Report, or use ADB to retrieve logs: adb shell bugreport
• Note your device ID, Esper Agent version, and Android OS version.
• Identify your app's supported architectures by running: aapt dump badging <your-app.apk> | grep abi

Still need help?

If you've tried the steps above and your app installation still fails, contact Esper Support. Provide your device ID, Esper Agent version, Android OS version, and the output of the aapt dump badging command from your app so our team can investigate further.