SIGSEGV in libGLESv2_mtk.so on FCNT arrows We2 devices

Submission checklist

• Confirmed on the latest rive-android version — affected hardware unavailable
• Searched the documentation and forums
• Searched existing issues; no duplicate found

Description

Rendering a Rive animation causes a native SIGSEGV on these FCNT arrows We2 models:

• FCG02 — au/UQ
• A402FC — SoftBank
• F-52E — docomo

Crashlytics reports the same blame frame across the affected models:

SIGSEGV
libGLESv2_mtk.so + 0x119230

The crash occurs on Rive's render thread, with the native trace passing through librive-android.so and libEGL.

In our app, this occurs shortly after startup when the learning path renders a Rive animation. The process terminates, and the crash can recur after relaunch, preventing affected users from reaching lessons.

We have observed this crash signature with:

• Rive Android 11.7.1
• Rive Android 11.8.0

We have not tested the latest Rive version on affected FCNT hardware.

Previous working version

None known on the affected devices and current firmware.

Reproduction steps / code

We cannot reproduce this on an emulator or on other Android hardware.

Observed production sequence:

1. Launch the app on FCG02, A402FC, or F-52E running Android 16.
2. Navigate to—or restore directly into—a screen containing a Rive animation.
3. The process terminates with the native crash above as the animation begins rendering.

No specific .riv file has been identified as the trigger.

Rive Android runtime version

11.7.1 and 11.8.0

Rive API

Legacy (RiveAnimationView)

Device

• FCNT arrows We2 FCG02
• FCNT arrows We2 A402FC
• FCNT arrows We2 F-52E

Device OS

Android 16, ARM64

App minimum SDK level

API 26

App target SDK level

API 36

App NDK level

Not explicitly pinned

Other Rive runtimes affected

Unknown

Additional context

The corresponding current carrier firmware versions are:

• FCG02: V54RK51B
• A402FC: V54RS51B
• F-52E: V54RD51B

Crashlytics does not include the device build number, so we cannot confirm the installed firmware for each individual event.

Start with the legacy RiveAnimationView path and the render thread through librive-android and libEGL. Investigate the SIGSEGV on the listed FCNT arrows We2 devices running Android 16, since no emulator or other hardware reproduces it and no triggering .riv file is known. Done means identifying a reproducible trigger or confirmed mitigation and verifying that affected animations no longer terminate the process.