App Bundle: MissingLibraryException
See original GitHub issueGoal
To find a solution for ABI related problems
Expected Results
To run all split versions of app successfully
Actual Results
Fatal Exception: java.lang.RuntimeException: Unable to create application my.app.AppMain: com.b.a.b: lib/armeabi/librealm-jni.so
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4715)
at android.app.ActivityThread.-wrap1(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1405)
Caused by com.b.a.b: lib/armeabi/librealm-jni.so
at com.b.a.a.a(ApkLibraryInstaller.java:85)
at com.b.a.d.a(ReLinkerInstance.java:180)
at com.b.a.d.a(ReLinkerInstance.java:136)
at com.b.a.c.a(ReLinker.java:1070)
at io.realm.internal.m.a(RealmCore.java:60)
at io.realm.v.a(Realm.java:258)
at my.app.AppMain.onCreate(AppMain.java:256)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1013)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4712)
at android.app.ActivityThread.-wrap1(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1405)
Version of Realm and tooling
Realm version(s): 5.1.0 Android Studio version: 3.2 canary 15
Which Android version and device: Nexus 5X tries to load x86, but most reported devices try armeabi Many different devices are affected App is not using other so files than Realm.
From the Google Play dashboard I can see that no armeabi version is generated, only the 5 that Realm uses.
Edit: removed the x86 from the stacktrace, that was confusing
Issue Analytics
- State:
- Created 5 years ago
- Comments:54 (21 by maintainers)
Top Results From Across the Web
com.getkeepsafe.relinker.MissingLibraryException: librealm ...
Couldn't load “librealm-jni.so” If your app uses other native ... pack .so files included in jar files (see Realm Java issue 1421).
Read more >[Solved]-com.getkeepsafe.relinker.MissingLibraryException
The workaround to this issue is to exclude Realm's ARM64 library from the APK file by adding the following code to the app's...
Read more >Automated Malware Analysis Report for app-release.apk
setDataAndType(n/a,"application/vnd.android.package-archive") ... MissingLibraryException" with parameters: [class java.lang.String]; 08-09 09:41:09.669 ...
Read more >Build and test your Android App Bundle
Build an app bundle using Android Studio; Deploy using app bundles with Android Studio; Build and test from the command line.
Read more >MissingLibraryException when using Realm - Issue Tracker
Experiencing issue when using App Bundles and Realm native libs. See attached APK analyzer screenshot for bundled realm native libs in the APK...
Read more >
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Unfortunately, I still get the same issue with Realm version 5.7.0.
Samsung SM-G965F LGE Nexus 5X
@Zhuinden the
MissingSplitsManager
didn’t work for me when I tried an APK withndk { abiFilters "mips" }
on a x86 emulator.Instead I’m catching the
RuntimeException
and show a toast.