App install fails with Null error on iMin devices: investigate ABI mismatch

Android

When deploying an app to an iMin device, the installation fails and the Esper Agent reports Encountered an error while trying to install the app - Null.

Why this happens

Every APK that uses native code bundles compiled libraries for specific processor architectures, known as ABIs. When the APK does not include a library compiled for the architecture your iMin device runs, Android rejects the install entirely. This mismatch becomes especially common after a firmware update that changes which ABIs the device reports as supported.

Steps to resolve

1. Confirm the error is an ABI mismatch. In the Esper Console, go to Devices & Groups → [Device Name] → Reports → Logs and look for the error code INSTALL_FAILED_NO_MATCHING_ABIS or res=-113. If you see a different error code, stop here and contact Esper Support with your logs, as the cause is unrelated to ABI.
2. Identify the architectures your device supports. You can do this two ways:
   • Esper Console: Go to Devices & Groups → [Device Name] → Device Info and locate the ABI or hardware fields.
   • ADB: Run the following commands against the device:

     adb shell getprop ro.product.cpu.abi
     adb shell getprop ro.product.cpu.abilist

     The output lists every architecture the device accepts, for example arm64-v8a.
3. Check whether the APK includes a matching native library. Rename the APK file to .zip and extract it, then open the lib/ directory. Each subdirectory name corresponds to a supported ABI, for example lib/arm64-v8a/. If the directory for your device's architecture is absent, the APK cannot install on that device.
4. Obtain a compatible APK.
   • If you own the source code, rebuild the APK with a splits or universalApk configuration that includes your device's ABI.
   • If the APK comes from a vendor or third party, contact them directly and request either a universal build or the architecture-specific variant that matches your device.
5. Upload and deploy the corrected APK. In the Esper Console, go to Apps & Configuration → Enterprise Apps → [App Name], click Add Version, and upload the compatible APK. Then deploy it to the affected devices.

Verify: In the Esper Console, go to Devices & Groups → [Device Name] → Apps. The app should appear in the installed apps list with an Active status and no error message within 5 minutes of deployment completing.

If this doesn't resolve it

If the installation still fails after deploying the corrected APK, or if your logs show an error code other than INSTALL_FAILED_NO_MATCHING_ABIS, contact Esper Support and include the following:

• The full log export from Devices & Groups → [Device Name] → Reports → Logs
• The ADB output from ro.product.cpu.abi and ro.product.cpu.abilist
• The APK filename and the source or vendor it came from

Still need help?

If you're still experiencing app install failures on your iMin devices, submit a support ticket and include the app's supported ABIs, your device's architecture (ARM or x86), and the full error logs from the Esper console.