`base/lib/arm64-v8a/librive_text.so` and `base/lib/x86_64/librive_text.so` are not compatible with 16KB native library alignment

[Tom3652]

Thanks for the package 🙏

I have received a warning from Google Play Console telling me this :

Recompile your app with 16 KB native library alignment
Your app uses native libraries that are not aligned to support devices with 16 KB memory page sizes. These devices may not be able to install or start your app, or your app may start and then crash.

There are new app bundles in this release that do not support 16 KB.

Android 15 supports devices with 16 KB memory page sizes, which can improve your app's performance. We recommend recompiling your app when you migrate to Android 15, and testing your app in a 16 KB environment to avoid issues for users.

And right below it tells me which libraries are in question : base/lib/arm64-v8a/librive_text.so and base/lib/x86_64/librive_text.so

Which seems to be from rive package, so can you support the 16 KB native library alignment please ?

[malinowa]

I've encountered the same error. Even after updating the package for the newest version (v0.13.20) it still looks like there is no 16KB native library alignment. Is there any proper workaround? We need to deploy app to Google Play asap.

[Goddchen]

This commit from Dec 2024 tries to fix this: 90c91f6
They just have to release it - please do 🙏
A side note to this PR: I don't think it will fix our issue. The official migration docs mention that only NDK r28 will fix it without any additional configuration. If you use r27, you still have to apply the fixes mentioned here: https://developer.android.com/guide/practices/page-sizes#compile-r27

[Tom3652]

I will release my app by raising the NDK to r28.xxx to be applied to rive and see if i still get the warning from Google Play Console, thanks for the info @Goddchen !

[Goddchen]

I will release my app by raising the NDK to r28.xxx to be applied to rive and see if i still get the warning from Google Play Console, thanks for the info @Goddchen !

@Tom3652 that is going to change anything. The Rive binary files come pre-built and are just used. When you change your NDK version, that only applies to stuff that you build from source.

[Tom3652]

Aah too bad alright thanks for the specification...

[alexcontra]

Hi @Goddchen I think if we open a PR with the changes from this commit it will be much faster.

[Goddchen]

Hi @Goddchen I think if we open a PR with the changes from this commit it will be much faster.

@alexcontra why would you think that? The commit is already on master, what would you put into that PR?

[alexcontra]

Hi @Goddchen sorry for that, i thought it's on a fix branch. Then yes, probably they just have to release it.

[HayesGordon]

The way our Flutter package is built is entirely different from our native Android runtime.

You can control which NDK version this Flutter package uses. We provide an optional override for the NDK version.

You can set it in your apps gradle.properties file, for example:

rive.ndk.version=27.2.12479018

Or any other version. But we recommend at least 25 or above.

This may require you also to update your app's ndk version (and I recommend setting it to the same value):

android {
  compileSdkVersion 31
  ndkVersion "27.2.12479018"
  ...
}

Note that our Rive Flutter package will migrate to use Rive Native for Flutter, which is an entirely different way that we distribute the native libs for Flutter (but we also still allow building them yourself). We'll likely add a similar option to allow you to specify the NDK version when manually building the libs.

We're encouraging customers to start adoption rive_native as we will soon be making a major release for this Rive Flutter package that migrates to Rive Native. You can read more about it here. The default libs that we ship for Rive Native for Flutter are using ndkVersion "27.2.12479018".

[Goddchen]

Thanks for taking a look @HayesGordon .
Let me explain our issues in a bit more detail.

rive

Setting the rive.ndk.version will not do anything for us, since the pre-built binaries com from pub.dev. There is nothing built when we do flutter build apk.... And the pre-built binaries that are downloaded from pub.dev are not 16KB aligned. So, unfortunately, your suggested fix will not work.

There is this commit: 90c91f6
This will likely fix our issue, because, hopefully, the pre-built binaries will then be 16KB aligned. But to be able to get them, you need to publish a release to pub.dev.

rive_native

I have multiple issues with this new package:

1. When using it, everything compiles fine, but when starting the app, it just immediately crashes back to the home screen without any meaningful error logs.
2. You are not providing binaries for x86_64. This is an issue for us. Or does it by any chance mean that some compatibility layer will use the ARM binaries on those devices?
3. I checked the downloaded pre-built binaries from this package and those are not 16KB aligned as well. So we face the same issue as with rive.

In your docs you describe a way to build the binaries by ourselves. Which might be working, but will require specific tooling on your machine. And since every user would need to do that, that's not really a way to go forward either.

So please, can you re-open this ticket? It is by no means completed or solved.

[Goddchen]

Just found a possible solution, which might be related to the issue with the r27 NDK that I mentioned earlier when I linked to the official Android 16KB documentation page.

The generated librive_text.so file will not be 16KB aligned if you use the r27 NDK, as you suggest.

Using the r28 NDK instead (in the app project as well as for rive) generates a 16KB aligned binary!

TLDR

Use NDK 28.1.13356709 in both, your app's build.gradle file (android { ndkVersion: "28.1.13356709" }) as well as in your gralde.properties file (rive.ndk.version=28.1.13356709). Note: you also need to add android.ndk.suppressMinSdkVersionError=21 to your gradle.properties file.

[HayesGordon]

@Goddchen, this Rive package does not have prebuilt libraries; it builds the lib when you build your app. On Pub we include the native source code as part of the rive_common package. You have full control over the NDK version used. This commit you linked only updates the NDK used for the example app for the Rive Flutter package, nothing to do with the package code.

For NDK 27 you would likely also need to do this: https://developer.android.com/guide/practices/page-sizes#compile-r27

Which is the link you posted earlier.

Interesting that the libs for rive_native aren't 16KB aligned! That will need some investigation on our side. Ideally, for rive_native, you would never need to build the libs yourself.

For rive_native are you experiencing this immediate crash on the latest version? Can you run the example app on Pub? If you can create a new issue for this it'll be great, and if you can share the conditions that are causing the crash (devices, environment, etc).

Regarding x86_64 support that is something we'll look into