Crashlytics Crash Reports - Instantaneous Crash on Certain Devices

[shubham-stan]

Description

An instantaneous crash on launch occurs on certain devices even when there is no code related to rive on the project. just bundling the package in the build causes this.

Devices I am aware of - Samsung - Galaxy M11, Note 10+ 5G, VIVO - V2101, Y71, OPPO - F17 PRO.

Fatal Exception: java.lang.RuntimeException: Unable to get provider androidx.startup.InitializationProvider: r0.b: sa.b: Could not find 'libjnirivebridge.so'. Looked for: [armeabi-v7a, armeabi], but only found: [].
at android.app.ActivityThread.installProvider(ActivityThread.java:5858)
at android.app.ActivityThread.installContentProviders(ActivityThread.java:5447)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5386)
at android.app.ActivityThread.-wrap2(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1546)

Additional context

This looks similar to realm/realm-java#6812

We have a bunch of features ready to pushed on production using rive but this crash has deterred us from rolling out to production. Can provide additional information if you could hint me in the right direction.

[HayesGordon]

Hi @shubham-stan, thanks for creating the issue.

We have a similar report on the Android runtime that mentions an initialisation issue, where one person mentioned it only occurs for Google test devices on the play store (so not actual users). Are you testing with a test-lab, or on physical devices you have with you?

We also just released v4.1.0 which bumps androidx.startup:startup-runtime, the fix for this issue in that release could also be the underlying problem.

[shubham-stan]

hi @HayesGordon,

We could not reproduce on our physical test devices (as we dont have the devices the crash was reported on - our physical test devices seem to work fine) but we received feedback on our discord and also we have logs on Crashlytics that basically tell us the app crashes on launch with the above error I shared. We will be bumping to 4.1.0 as suggested and will keep you posted on this. This is pretty much essential to our app and we are looking forward to sending features using rive to production. This crash is inhibiting this currently.

[HayesGordon]

Thanks for getting back to us @shubham-stan. Please let me know what you find with 4.1.0 and I'll forward this to the rest of the team.

[Lukmannudin]

I am experiencing a similar issue, @shubham-stan, with version 9.3.6.

The error message is:
Unable to get provider androidx.startup.InitializationProvider: k3.c: Fe.b: Could not find 'librive-android.so'. Looked for: [arm64-v8a, armeabi-v7a, armeabi], but only found: [].

cc: @HayesGordon

[HayesGordon]

Hi @Lukmannudin, do you have a reproducible example? If so, could you please share that? We can investigate initializing Rive differently for the React Native runtime.

[jleprinc]

Still hapening on version 7.2.0, I see there is a new version of androidx.startup:startup-runtime : 1.2.0, could it fix it?