16KB page size alignment failure with Realm on Android (Target SDK 35)

[kadhar03]

How frequently does the bug occur?

Always

Description

Issue: 16KB ELF alignment failure with Realm on Android 15 (Target SDK 35)

We are trying to build our React Native app using:

React Native: 0.79.5
Realm JS: 20.1.0
Target SDK: 35 (Android 15)
NDK: r27

We are seeing that the app fails validation on devices with 16KB page size, introduced in Android 15.
On running check_elf_alignment.sh, we see multiple .so libraries (like librealm.so) reported as UNALIGNED with alignment.

We have tried the following:

Added -Wl,-z,max-page-size=16384 linker flag in build.gradle.

Verified that externalNativeBuild is picking the flags.

Used APK Analyzer and confirmed unaligned native libraries.

Please provide an recommended way to build Realm native libraries aligned to 16KB for Android 15+

Stacktrace & log output

APK is not compatible with 16 KB devices. Some libraries have LOAD segments not aligned at 16 KB boundaries:
lib/arm64-v8a/librealm.so

Can you reproduce the bug?

Always

Reproduction Steps

No response

Version

20.1.0

What services are you using?

Atlas Device Sync

Are you using encryption?

Yes

Platform OS and version(s)

Android

Build environment

Which debugger for React Native: 0.79.5

Cocoapods version

No response

[liamjones]

@kraenhansen excuse the direct ping; am I right in suspecting the issue here is that realm-core is prebuilt and downloaded when the realm node module installs?

[liamjones]

Okay, it doesn't look like it needs realm-core changes. I believe I have it working in realm-js, I just need to do some testing to confirm it doesn't appear broken and I'll post details.

[liamjones]

Can you try patching your realm locally with #7019 (it's a one-line change in your node_modules/realm files) and see if it works for you? I've tested it in an empty 0.79.5 app using yarn android and check_elf_alignment.sh on a 16KB page size emulator but I've not packaged a real app for both 32 & 64 bit architectures yet.

[kadhar03]

Hi @liamjones ,

Yes, I tested it by creating a local patch with the change from PR #7019, and it works fine on my end. I applied the patch in node_modules/realm and verified it on a 16KB page size using check_elf_alignment.sh. Everything looks good so far — thanks for the reference.
I'l Shared the attchment for your reference

Can you try patching your realm locally with #7019 (it's a one-line change in your node_modules/realm files) and see if it works for you? I've tested it in an empty 0.79.5 app using yarn android and check_elf_alignment.sh on a 16KB page size emulator but I've not packaged a real app for both 32 & 64 bit architectures yet.

[santana20]

how to solving? i try install realm version 12.4.2, 20.1.0 in react native 0.79.5 using target SDK 35 always force close when import "Realm"

[hieupham95]

@liamjones
I’m also experiencing the same issue when using version 10.17.0.
It throws the following error:
java.lang.UnsatisfiedLinkError: dlopen failed: empty/missing DT_HASH/DT_GNU_HASH in "/data/data/com.vib.myvib2.dev/app_lib/librealm-jni.so.10.17.0" (new hash type from the future?)

How can I resolve this on Android using Kotlin?

[kraenhansen]

@hieupham95 librealm-jni.so is not produced by the Realm JS project, that's an artifact from Realm Java / Kotlin:
See realm/realm-java#7894 for something which looks more similar to what you're experiencing.