Many Crashes on tv and phones: UnsatisfiedLinkError.

[nikolaychukmax]

Description

We are redesigning big app of ours using rive animations.
Right now we are having rollout of 3% and already heaving huge amount of crashes.

Crash: Fatal Exception: java.lang.UnsatisfiedLinkError
No implementation found for long app.rive.runtime.kotlin.core.FileAssetLoader.constructor() (tried Java_app_rive_runtime_kotlin_core_FileAssetLoader_constructor and Java_app_rive_runtime_kotlin_core_FileAssetLoader_constructor__).
Note: we are using fallback:

private fun initRive() {
        try {
            Rive.init(this)
        } catch (ex: UnsatisfiedLinkError) {
            ReLinker.loadLibrary(this, "rive-android", object : ReLinker.LoadListener {
                override fun success() {
                    Rive.initializeCppEnvironment()
                }

                override fun failure(t: Throwable?) {
                    addLog("Failed to init RIVE")
                }
            })
        }
    }

This was supposed fix for this crash:
Fatal Exception: java.lang.UnsatisfiedLinkError
dlopen failed: unknown reloc type 17 @ 0x82cb4014 (11274)
on Rive.init(context)

Versions, Device, and Other Information

• Rive Android Runtime Version: version tested is the latest for now 11.2.1
• Rive API: compose
• Device:

and more - App Minimum SDK Level: 24 - App Target SDK Level: 36 - App NDK Level: not specified. - Frequency: too often for 3% rollout

App has moduels with native libraries: OpenVpn, WireGuard, Xray, Ikev.

Reproduction Steps

This is early crash on initialisation, so unknown. And before loading any .riv file.

Expected Behavior

Working App

Screenshots

Additional context

Please ask any questions, so this will resolve faster

[Toubap]

I face exactly the same issue
Rive version : 11.2.1

[tylernij]

Hello, we're aware of this issue and are still working on it. We're experimenting with some fixes. I'll come back and update when this is fixed 👍

[Toubap]

Hello
I see you released a new version (11.3.0). Does this one fix the issue? Should I release a new version of my app with this update?
Thank you

[nikolaychukmax]

Hello I see you released a new version (11.3.0). Does this one fix the issue? Should I release a new version of my app with this update? Thank you

All changes are listed in release notes. As developer mentioned, they are aware of issue and will update on any news.

[PavlosTze]

We are also seeing hundreds of issues on Android 9:

We had to revert back to 10.4.4 which was working OK (the crashes are on 11.2.1).

By the way, LLMs gave that explanation if that helps:

You’re crashing because of a native linker incompatibility in Rive during app startup, not because of app logic.

• The crash path is App.onCreate -> AppInitializer.initializeComponent(RiveInitializer)
• Rive then calls System.loadLibrary(“rive-android”) and fails with unknown reloc type 17.
• Your app version includes app.rive:rive-android:11.2.1 (gradle/libs.versions.toml:76), and release 9.4 contains that version.
• In 11.2.1, librive-android.so for armeabi-v7a has a relocation entry of type 17 at index 11274; your crash log shows exactly (11274), which matches that entry.
• On ARM32, relocation type 17 is R_ARM_TLS_DTPMOD32; Android 9 / API 28 linker does not support that reloc type and throws this exact error.
• Because you initialize Rive in Application, affected devices crash immediately on launch.
  So the reason is: Rive 11.2.1 native ARM32 library is incompatible with the API 28 linker, and your app eagerly initializes Rive at startup.
  If you want, I can next outline the safest mitigation options (rollback version vs armv7 exclusion vs guarded init fallback).

[ErikUggeldahl]

Hi @PavlosTze. This agrees with my findings as well. I've found a tentative build config change that removes the relocations and makes them emulated instead (EMUTLS). I'm currently on vacation and will polish it up for release when I'm back, likely late next week. Thank you for you patience.

[PavlosTze]

Hi @PavlosTze. This agrees with my findings as well. I've found a tentative build config change that removes the relocations and makes them emulated instead (EMUTLS). I'm currently on vacation and will polish it up for release when I'm back, likely late next week. Thank you for you patience.

No worries, thanks for the reply. Have a great vacation!