You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Unable to get provider androidx.startup.InitializationProvider: androidx.startup.StartupException: com.getkeepsafe.relinker.MissingLibraryException: Could not find 'librive-android.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: []. #323
Hi @Pranathi-Cumulations this has been reported here and it is currently believed to be related only to Play Store devices and not to real users.
Going to close this issue for now, if you have a more detailed report and a repro we'd be happy to take a look at this!
Reacted by Daniel, Jameson Williams, Charlotte Margaret, Claire Liew, lasfito, yurii-bereza, vegeta2102, shawn-emerge, Yes Adilov, Ethan Neff and 1 more
Hi, thanks for the reply, but I am pretty sure that some of them are not
play Store devices.Because I have not uploaded any build to play store in
that period wheb the crash happened
@umberto-sonnino same issue happening for me in real devices. more than 30 users. spiking this issue now. please give me the solution.
Rive Version:
implementation 'app.rive:rive-android:9.0.10'
Log details: Fatal Exception: java.lang.RuntimeException
Unable to get provider androidx.startup.InitializationProvider: androidx.startup.StartupException: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "stderr" referenced by "librive-android.so"...
Caused by androidx.startup.StartupException
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "stderr" referenced by "librive-android.so"...
It seems this issue still persists. Although I can't reproduce it on my end, we've received several reports from version 9.3.6 indicating the following error:
"Could not find 'librive-android.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: []."
@jamesonwilliams We recently released an improvement to ReLinker where we now include the recursively() flag. This was in 10.1.6. Could you give that a try and see if it improves things for you?
@ErikUggeldahl@umberto-sonnino it seems this issue Caused by androidx.startup.StartupException
com.getkeepsafe.relinker.MissingLibraryException: Could not find 'librive-android.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: [].
We are seeing the same error when using rive-react-native version 9.5.0 which internally uses rive-android 10.4.1. This is the error:
Fatal Exception: java.lang.RuntimeException: Unable to get provider androidx.startup.InitializationProvider: androidx.startup.StartupException: com.getkeepsafe.relinker.MissingLibraryException: Could not find 'librive-android.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: []
We do still get a related error at relatively low rate on Rive 10.4.4.
Fatal Exception: java.lang.RuntimeException: Unable to get provider androidx.startup.InitializationProvider: retrofit2.HttpException: retrofit2.HttpException: Could not find 'librive-android.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: [].
at android.app.ActivityThread.installProvider(ActivityThread.java:7307)
at android.app.ActivityThread.installContentProviders(ActivityThread.java:6843)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6753)
at android.app.ActivityThread.access$1300(ActivityThread.java:244)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1921)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7719)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
I'm still facing this issue on Pixel 6 Pro (Android 12)
Fatal Exception: java.lang.RuntimeException
Unable to get provider androidx.startup.InitializationProvider: androidx.startup.StartupException: com.getkeepsafe.relinker.MissingLibraryException: Could not find 'librive-android.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: [].
Fatal Exception: java.lang.RuntimeException
Unable to get provider androidx.startup.InitializationProvider: androidx.startup.StartupException: com.getkeepsafe.relinker.MissingLibraryException: Could not find 'librive-android.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: [].
Caused by com.getkeepsafe.relinker.MissingLibraryException: Could not find 'libandroid.so'. Looked for: [armeabi-v7a, armeabi], but only found: [].
This issue has 26 crash events affecting 7 users for last 7 days.
88% Android 9
12% Android 8
Device states are 23% background
35% Samsung
27% Huawei
23% Xiaomi
15% ZTE
Lib version is "11.1.0"
One of the stacktrace:
Caused by com.getkeepsafe.relinker.MissingLibraryException: Could not find 'libandroid.so'. Looked for: [armeabi-v7a, armeabi], but only found: [].
at com.getkeepsafe.relinker.MissingLibraryException.<init>(MissingLibraryException.java:22)
at com.getkeepsafe.relinker.ApkLibraryInstaller.installLibrary(ApkLibraryInstaller.java:175)
at com.getkeepsafe.relinker.ReLinkerInstance.loadLibraryInternal(ReLinkerInstance.java:180)
at com.getkeepsafe.relinker.ReLinkerInstance.loadLibrary(ReLinkerInstance.java:136)
at com.getkeepsafe.relinker.ReLinkerInstance.loadLibrary(ReLinkerInstance.java:92)
at com.getkeepsafe.relinker.ReLinkerInstance.loadLibraryInternal(ReLinkerInstance.java:197)
at com.getkeepsafe.relinker.ReLinkerInstance.loadLibrary(ReLinkerInstance.java:136)
at com.getkeepsafe.relinker.ReLinkerInstance.loadLibrary(ReLinkerInstance.java:92)
at app.rive.runtime.kotlin.core.Rive.init(Rive.kt:57)
at app.rive.runtime.kotlin.core.Rive.init$default(Rive.kt:46)
at app.rive.runtime.kotlin.RiveInitializer.create(RiveInitializer.kt:38)
at app.rive.runtime.kotlin.RiveInitializer.create(RiveInitializer.kt:36)
at androidx.startup.AppInitializer.doInitialize(AppInitializer.java:180)
at androidx.startup.AppInitializer.discoverAndInitialize(AppInitializer.java:239)
at androidx.startup.AppInitializer.discoverAndInitialize(AppInitializer.java:207)
at androidx.startup.InitializationProvider.onCreate(InitializationProvider.java:49)
at android.content.ContentProvider.attachInfo(ContentProvider.java:1952)
at android.content.ContentProvider.attachInfo(ContentProvider.java:1927)
at android.app.ActivityThread.installProvider(ActivityThread.java:6638)
at android.app.ActivityThread.installContentProviders(ActivityThread.java:6147)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6062)
at android.app.ActivityThread.access$2000(ActivityThread.java:225)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1802)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:192)
at android.app.ActivityThread.main(ActivityThread.java:7049)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:913)
Activity
umberto-sonnino commentedon Apr 3, 2024
Hi @Pranathi-Cumulations this has been reported here and it is currently believed to be related only to Play Store devices and not to real users.
Going to close this issue for now, if you have a more detailed report and a repro we'd be happy to take a look at this!
Pranathi-Cumulations commentedon Apr 3, 2024
harisAsterbyte commentedon Apr 17, 2024
@umberto-sonnino same issue happening for me in real devices. more than 30 users. spiking this issue now. please give me the solution.
Rive Version:
implementation 'app.rive:rive-android:9.0.10'
Log details:
Fatal Exception: java.lang.RuntimeException
Unable to get provider androidx.startup.InitializationProvider: androidx.startup.StartupException: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "stderr" referenced by "librive-android.so"...
Caused by androidx.startup.StartupException
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "stderr" referenced by "librive-android.so"...
Caused by java.lang.UnsatisfiedLinkError
_dlopen failed: cannot locate symbol "stderr" referenced by "librive-android.so"...
com.getkeepsafe.relinker.SystemLibraryLoader.loadPath (SystemLibraryLoader.java:31)_
com.getkeepsafe.relinker.ReLinkerInstance.loadLibraryInternal (ReLinkerInstance.java:206)
com.getkeepsafe.relinker.ReLinkerInstance.loadLibrary (ReLinkerInstance.java:136)
com.getkeepsafe.relinker.ReLinker.loadLibrary (ReLinker.java:70)
com.getkeepsafe.relinker.ReLinker.loadLibrary (ReLinker.java:51)
app.rive.runtime.kotlin.core.Rive.init (Rive.kt:42)
app.rive.runtime.kotlin.core.Rive.init$default (Rive.kt:37)
app.rive.runtime.kotlin.RiveInitializer.create (RiveInitializer.kt:34)
app.rive.runtime.kotlin.RiveInitializer.create (RiveInitializer.kt:32)
androidx.startup.AppInitializer.doInitialize (AppInitializer.java:180)
Devices
Lukmannudin commentedon Jun 9, 2024
Hi @umberto-sonnino,
It seems this issue still persists. Although I can't reproduce it on my end, we've received several reports from version 9.3.6 indicating the following error:
"Could not find 'librive-android.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: []."
jamesonwilliams commentedon Jun 10, 2025
Still a thing in 10.1.3. Seems to happen on Google Pixel 6 Pro / Android 12 or earlier
ErikUggeldahl commentedon Jun 10, 2025
@jamesonwilliams We recently released an improvement to ReLinker where we now include the
recursively()flag. This was in 10.1.6. Could you give that a try and see if it improves things for you?jamesonwilliams commentedon Jun 10, 2025
@ErikUggeldahl Ah, very cool! Yes, we'll give this a try and report back.
15189611 commentedon Sep 15, 2025
@jamesonwilliams Was the issue resolved on 10.1.6? We also have this issue on 9.11.3, pls
15189611 commentedon Sep 15, 2025
@ErikUggeldahl @umberto-sonnino it seems this issue Caused by androidx.startup.StartupException
com.getkeepsafe.relinker.MissingLibraryException: Could not find 'librive-android.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: [].
anirudhsama commentedon Sep 15, 2025
We are seeing the same error when using
rive-react-nativeversion 9.5.0 which internally usesrive-android10.4.1. This is the error:Fatal Exception: java.lang.RuntimeException: Unable to get provider androidx.startup.InitializationProvider: androidx.startup.StartupException: com.getkeepsafe.relinker.MissingLibraryException: Could not find 'librive-android.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: []
cc @ErikUggeldahl
chabroncano commentedon Sep 18, 2025
Hi @umberto-sonnino we are encountering similar issue, we are at 10.3.0
We would appreciate if you could reopen this issue as this is clearly still happening, we are getting more and more crash reports. 🙏
sahilpocketfm commentedon Nov 6, 2025
I'm facing the same issue on 10.4.4 version. Any solution for this?
jamesonwilliams commentedon Nov 6, 2025
We do still get a related error at relatively low rate on Rive 10.4.4.
lasfito commentedon Nov 28, 2025
Why was this issue closed? its still happening and its not just play store devices like someone claimed.
vegeta2102 commentedon Jan 20, 2026
I'm still facing this issue on Pixel 6 Pro (Android 12)
gareys commentedon Jan 29, 2026
+1 Seeing this as well for android 12 users
Please reopen the issue
Velord commentedon Feb 6, 2026
Caused by com.getkeepsafe.relinker.MissingLibraryException: Could not find 'libandroid.so'. Looked for: [armeabi-v7a, armeabi], but only found: [].This issue has 26 crash events affecting 7 users for last 7 days.
88% Android 9
12% Android 8
Device states are 23% background
35% Samsung
27% Huawei
23% Xiaomi
15% ZTE
Lib version is "11.1.0"
One of the stacktrace:
If you need more info feel free to ask.
tylernij commentedon Feb 24, 2026
Hello, we're actively looking into this and it's a top priority. We'll come back and update when there's a resolution.
feat: add RiveRuntime API for Android init failure handling (#153)