rive-android icon indicating copy to clipboard operation
rive-android copied to clipboard

Published 20 hours ago • verified publisher icon rive-app

Crash on some devices while initialising Rive

Open kancic opened this issue 2 years ago • 7 comments

Description

I keep seeing this crash in Firebase on some devices, and I cannot reproduce it. It happens while initialising Rive in the Application's onCreate:

Fatal Exception: java.lang.UnsatisfiedLinkError: dlopen failed: library "libndk_translation_proxy_libGLESv3.so" not found
       at java.lang.Runtime.load(Runtime.java:332)
       at java.lang.System.load(System.java:1069)
       at com.getkeepsafe.relinker.SystemLibraryLoader.loadPath(SystemLibraryLoader.java:31)
       at com.getkeepsafe.relinker.ReLinkerInstance.loadLibraryInternal(ReLinkerInstance.java:204)
       at com.getkeepsafe.relinker.ReLinkerInstance.loadLibrary(ReLinkerInstance.java:136)
       at com.getkeepsafe.relinker.ReLinker.loadLibrary(ReLinker.java:70)
       at com.getkeepsafe.relinker.ReLinker.loadLibrary(ReLinker.java:51)
       at app.rive.runtime.kotlin.core.Rive.init(Rive.kt:30)

Device & Versions

  • Devices: Nexus 5X, Oneplus One
  • SDK Level: Api level 23
  • Rive version: 4.2.2

kancic avatar Feb 13 '23 14:02 kancic

We are also seeing this on a Nexus 5X in Crashlytics

PhilippNowak96 avatar Mar 02 '23 07:03 PhilippNowak96

We are also seeing this, Nexus 5X and Rive 4.0.0

chip2n avatar Mar 10 '23 09:03 chip2n

This might be related to our library using GLES3. Do you know if the devices you're seeing this on are restricted to GLES2?

umberto-sonnino avatar Mar 21 '23 11:03 umberto-sonnino

They should support GLES3

kancic avatar Mar 22 '23 12:03 kancic

And I have this in my manifest

<uses-feature
        android:glEsVersion="0x00030000"
        android:required="true" />

kancic avatar Mar 22 '23 12:03 kancic

Looks like it's mainly happening on devices Google uses for testing when you upload your app to the Playstore. We just uploaded a new release with partial rollout and the crash timestamp does not match to a real user already having the app, although we don't see anything in the prelaunch reports or something like that.

PhilippNowak96 avatar Mar 30 '23 11:03 PhilippNowak96

Looks like it's mainly happening on devices Google uses for testing when you upload your app to the Playstore. We just uploaded a new release with partial rollout and the crash timestamp does not match to a real user already having the app, although we don't see anything in the prelaunch reports or something like that.

Oh, interesting. I'm curious if other folks in the thread have seen a similar pattern or if they have reports from actual devices.

umberto-sonnino avatar Mar 30 '23 16:03 umberto-sonnino