Bump bundled rive-android to ≥ 11.5.0 for the libandroid.so startup-crash fix
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- android, react-native, typescript
- Domain
- build-system, mobile
Research direction
Search the repository for the runtimeVersions.android definition and inspect how the bundled rive-android version is selected. Update it to at least 11.5.0, ideally 11.7.1, then verify the generated Android dependency uses that version and covers the reported libandroid.so startup-crash case.
Written by the indexing model from the issue text.
Description
Submission checklist
- I have confirmed the issue is present in the latest version of
rive-react-native - I have searched the documentation and forums and could not find an answer
- I have searched existing issues and this is not a duplicate
Description
Bump bundled rive-android to ≥ 11.5.0 for the libandroid.so startup-crash fix
rive-react-native@9.8.3 still pins rive-android 11.4.1. The fix for the common startup crash
MissingLibraryException: Could not find 'libandroid.so'. Looked for: [armeabi-v7a, armeabi], but only found: [].
at app.rive.runtime.kotlin.RiveInitializer.create
landed in rive-android 11.5.0 (#12293, non-recursive linking) — so it's unreachable from any released wrapper (11.4.1 < 11.5.0).
Request: bump runtimeVersions.android to ≥ 11.5.0 (ideally 11.7.1).
Crash fires at startup via RiveInitializer, killing the app before RN loads — a top Android crash for us on low-end devices. Refs: rive-app/rive-android#323, #341.
rive-react-native version
9.8.3
React Native version
0.81.5
Expo setup
Expo prebuild
Expo SDK version
54
Device
Samsung Galaxy J4 Core (SM-J410F), armeabi-v7a — also seen on Hisense / low-end 32-bit devices
OS version
Android 8.1
- Dominant language
- TypeScript
- Stars
- 783
- Forks
- 81
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rive-app/rive-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
rive-app/rive-react-native#431 · 2 comments ·
-
[Android] Rive events dispatched off the UI thread can deadlock with Reanimated under Fabric (ANR) Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
rive-app/rive-react-native#444 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
rive-app/rive-react-native#441 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rive-app/rive-react-native#440 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
rive-app/rive-react-native#439 ·
All issues in rive-app/rive-react-native
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·