Datatrans SDK contains unaligned card.io libraries for 16KB page size

[ZayetsA]

Datatrans SDK contains unaligned card.io libraries for 16KB page size

Problem

The Datatrans SDK includes card.io Credit Card Scanner libraries (io.card:android-sdk) that use 4KB alignment (2^12) instead of the required 16KB alignment (2^14) for Android 16KB page size support.

Affected Libraries (from card.io bundled in Datatrans SDK)

• libopencv_core.so
• libopencv_imgproc.so
• libcardioRecognizer.so
• libcardioRecognizer_tegra2.so
• libcardioDecider.so

Workaround

Excluding the io.card:android-sdk dependency resolves all alignment issues.

Solution Needed

card.io SDK libraries need to be rebuilt to support 16KB page size devices.

Evidence

App crashes with native crash when trying to open card scanner on Android 16 with 16KB page size enabled.

Found 15 unaligned libs (only arm64-v8a/x86_64 libs need to be aligned).

[BasilAch]

Hello @ZayetsA, thank you for your report. Is the crashing device an x86 emulator?

Looking at your apk output, the only unaligned arm64-v8a ELF files are from your gaming library and Jetpack DataStore. On any real Android device and arm64 emulators the bundled card.io library should work just fine.

Regarding Play Store alignment requirements later this year, we will review the situation and either update card.io or remove support entirely. To be compliant, you can just exclude the unaligned x86 part already (and not use the scanner in your emulator, which is not very useful anyway):

android {
    packaging {
        jniLibs {
            excludes += ['**/x86_64/libcardio*.so', '**/x86_64/libopencv*.so']
        }
    }
}

Please note

card.io is an abandoned project that is unable to scan modern-style cards. We highly recommend switching to the Google card scanner, which can read almost all cards reliably. To do so, exclude card.io from your project and set up Google Pay for your app (with or without actually using Google Pay as a payment method).

[ngallazzi]

@BasilAch thanks for the answer, same issue on my side. Is there any scheduled date for the library update?

[evgeny]

@BasilAch Thank you for the hint. I tried the proposed approach and replaced card.io with Google Pay. Unfortunately, the button to scan the credit card disappears. The "Scan new card" button is still available in the Gboard keyboard, which provides the scan results to the SDK, but only when Gboard is set as the default keyboard. Is there any way to show the Datatrans scan button again without using Card.io?

[bacherma]

@evgeny Have you been able to figure it out? If the scan button is not present it means Google Pay has not been set up for production access. You have to apply as described here: https://developers.google.com/pay/api/android/guides/test-and-deploy/publish-your-integration

[bacherma]

We have released version 3.9.4 with an updated card.io library aligned to 16 KB pages.

As mentioned earlier, we recommend setting up your app to use the more advanced Google card scanner.