Closed Pranathi-Cumulations closed 2 months ago
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!
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
On Wed, Apr 3, 2024, 8:59 PM Umberto Sonnino @.***> wrote:
Hi @Pranathi-Cumulations https://github.com/Pranathi-Cumulations this has been reported here https://github.com/rive-app/rive-android/issues/305 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!
— Reply to this email directly, view it on GitHub https://github.com/rive-app/rive-android/issues/323#issuecomment-2034928386, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5BHJDM6HTWAQFPT3XBTWYLY3QN4ZAVCNFSM6AAAAABFRNQNUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZUHEZDQMZYGY . You are receiving this because you were mentioned.Message ID: @.***>
@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
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: []."
I am facing the above issue with google devices mainly Pixel 6 pro , not able to reproduce it but got noticed in the firebase crashlytics
Using version 8.7.0
Device Brand:Google Model:Pixel 6 Pro Orientation:Portrait RAM free: 1.91 GB Disk free: 1.56 GB
Using the Manifiest method to initialize