Rive-android 10.4.2: Native libraries not aligned for 16KB page sizes despite using NDK27
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- build-system, mobile
Research direction
Start by reproducing the issue with rive-android 10.4.2 and inspect the AAR's lib/x86/librive-android.so and armeabi-v7a/librive-android.so using APK Analyzer or Google Play Console. Compare the native libraries' LOAD section alignment against the expected 16KB alignment, and confirm that the packaged libraries no longer produce UNALIGNED warnings.
Written by the indexing model from the issue text.
Description
Description
The Rive Android library version 10.4.2 claims to support 16KB page sizes by using NDK27, but the precompiled native libraries in the AAR are still not properly aligned for
16KB page sizes, causing Google Play Console warnings and potential compatibility issues with Android 15+ devices.
Version Information
- rive-android version: 10.4.2
- Android Gradle Plugin (AGP): 8.8.2
- NDK version: Project uses latest NDK
- Compile SDK: 35
- Target SDK: 35
- Min SDK: 24
Steps to reproduce
- Add implementation(libs.rive) with version 10.4.2 to an Android project
- Build an APK/AAB targeting Android 15 (API 35)
- Analyze the APK with APK Analyzer or upload to Google Play Console
- Check the native library alignment warnings
lib/x86/librive-android.so: \e[31mUNALIGNED\e[0m (2**12)
armeabi-v7a/librive-android.so: \e[31mUNALIGNED\e[0m (2**12)
Expected behavior
When analyzing the APK/AAB with Google Play Console or APK Analyzer, all native libraries (.so files) from Rive should show proper 16KB page size alignment (16KB LOAD section alignment) for arm64-v8a and x86_64 architectures.
Additional context
According to Android documentation, NDK r28+ compiles with 16KB alignment by default,
- Dominant language
- Kotlin
- Stars
- 542
- Forks
- 66
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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-android
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
rive-app/rive-android#475 ·
-
Difficulty 3/5 Half a day Newbie friendliness 74/100
rive-app/rive-android#474 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
rive-app/rive-android#472 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
rive-app/rive-android#471 ·
-
SIGSEGV in libGLESv2_mtk.so on FCNT arrows We2 devicesPossibly taken @ErikUggeldahl claimed this 17 days ago. Openbug confirmed
Difficulty 4/5 3-5 days Newbie friendliness 30/100
rive-app/rive-android#468 · 5 comments · 3 reactions · 1 assignee ·
All issues in rive-app/rive-android
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lugassawan/swe-workbench#799 ·
Maintainers usually reply within 1 day
-
Default book icon displayed while loadingPossibly taken @Bhaskar-Guthula-137 claimed this today. Openbug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
kiwix/kiwix-android#5194 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
d4rken-org/butler#300 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
jellyfin/jellyfin-androidtv#5885 ·
Maintainers usually reply within 1 day