Fix Android App Crashes from Incompatible Native Libraries (ABI Mismatch)

Open the app and trigger the action that crashes it. While the crash occurs, run the following command on your PC:

adb logcat -d | grep -i "dlopen" > crash_log.txt

The -d flag dumps the current buffer and exits, while grep -i "dlopen" filters for library‑loading errors. Open crash_log.txt in a text editor and look for lines similar to:

java.lang.UnsatisfiedLinkError: dlopen failed: library "libexample.so" not found for "armeabi‑v7a"

If you see a line mentioning dlopen failed and an ABI, you have identified an ABI mismatch.

Obtain the APK file. If the app is installed from the Play Store you can pull it with:

adb shell pm path com.example.app

Copy the path that follows package:, then pull the file:

adb pull /data/app/com.example.app-1/base.apk ~/Desktop/example.apk

Now inspect the lib/ folder inside the APK:

unzip -l ~/Desktop/example.apk | grep "lib/"

The output will list directories such as lib/armeabi-v7a/ or lib/arm64-v8a/. Note which ABIs are present.

Run the following commands on the device via ADB:

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

The first property is the primary ABI (e.g., arm64-v8a), the second is a fallback (e.g., armeabi-v7a). Some devices also expose ro.product.cpu.abilist with a comma‑separated list of all supported ABIs.

Compare this list with the ABIs you discovered in the APK. If the device’s primary ABI is not represented in the APK, the loader will try the fallback; if neither matches, you get the crash.

Check the app’s Play Store page or the developer’s website for a “Universal” or “ARM64” download. Verify the file’s integrity (SHA‑256 checksum) before installing.

Install the new APK:

adb install -r ~/Downloads/example-universal.apk

The -r flag replaces the existing installation while keeping its data.

This method assumes you have the source code (open‑source app or your own project). Open the project in Android Studio and locate the build.gradle for the app module.

android {
    defaultConfig {
        ndk {
            // Add the missing ABI, for example armeabi‑v7a
            abiFilters "armeabi-v7a", "arm64-v8a"
        }
    }
}

Sync the project, then build a release APK:

./gradlew assembleRelease

The generated APK will now contain lib/armeabi‑v7a/ (or whichever ABI you added). Transfer it to the device and install with adb install -r as shown above.

If you do not have source code, you can still extract the existing native libraries, add the missing ones, and repack the APK using tools like apktool. This is more advanced and may violate the app’s license, so proceed only with apps you own or that are explicitly open‑source.

Google Play delivers split APKs (one for each ABI). You can fetch the full set with the bundletool utility.

# Install bundletool (requires Java)
wget https://github.com/google/bundletool/releases/download/1.15.0/bundletool-all-1.15.0.jar -O bundletool.jar
# Download the app’s .aab from the Play Store (requires a paid account) or obtain it from the developer.
# Then generate a universal APK:
java -jar bundletool.jar build-apks --bundle=example.aab --output=example.apks --mode=universal
# Extract the universal APK:
unzip example.apks universal.apk -d ./
# Install:
adb install -r universal.apk

This produces an APK that contains every native library, guaranteeing compatibility at the cost of a larger file.

Launch the app and repeat the action that previously crashed it. If the app stays open, run adb logcat again to confirm that no dlopen failed lines appear.

Optionally, you can double‑check the installed APK’s ABIs with:

adb shell pm path com.example.app
adb pull /data/app/com.example.app-1/base.apk ~/Desktop/installed.apk
unzip -l ~/Desktop/installed.apk | grep "lib/"

The list should now include the ABI that matches your device.