Android Mobile Payments SDK 2.7.0: libbugsnag-root-detection.so fails 16 KB RELRO check

Hi Square team,

We’re preparing a new Android app on Mobile Payments SDK 2.7.0 (through mobile-payments-sdk-react-native 2026.11.1) and checked it against Google’s 16 KB page size guidance before our first Play upload.

We checked every native library in our build against Google’s 16 KB guidance. All are 16 KB aligned, and all pass the RELRO check except two. One of them ships inside mobile-payments-sdk 2.7.0:

  • libbugsnag-root-detection.so (arm64-v8a and x86_64)
  • Built with NDK r23b
  • LOAD segments are 16 KB aligned, but the PT_GNU_RELRO segment ends at 0x5000, which is not a multiple of 0x4000 and does not fill the rest of its LOAD segment. Google’s page-size guide says this can cause SIGSEGV on 16 KB devices and typically comes from building with NDK r27 or lower without the 16 KB linker flags.

Questions:

  1. Is a version of the SDK with this library rebuilt (NDK r28 or later, or with -Wl,-z,max-page-size=16384 and -Wl,-z,common-page-size=16384) planned, and roughly when?
  2. Google Play says updates that don’t support 16 KB page sizes can’t be released from February 1, 2027. Will the SDK be fully compliant before then?
  3. Is there anything we should do on our side in the meantime?

Thanks.

John

Hi John,

Thanks for the detailed report.

Square added 16 KB support in MPSDK 2.3.2 and the 0x5000 endpoint is confirmed, but in the published 2.7.0 files, RELRO covers the entire writable LOAD and extends into padding, with no trailing writable data matching the guide’s SIGSEGV scenario. Both pass the current Android Studio source’s ELF-checking logic, which handles this case beyond the guide’s endpoint formula.

In the meanwhile, you can test the release build on a verified 16 KB device or emulator and check its Play Console validation before your first release. Changing app-level linker flags won’t rebuild bundled SDK libraries.