Linux aarch64 isn't supported [358045505]

Fixed

Bug

Status Update

No update yet.

Description

me...@ralph.ms

created issue #1

Aug 7, 2024 04:49PM

Component used: androidx.sqlite, androidx.room<br>

Version used: androidx.sqlite 2.5.0-alpha04, androidx.room 2.7.0-alpha04

Devices/Android versions reproduced on: Linux aarch64 devices such as RaspberryPi.

The following error occurred when using the Room library with a JVM application running on a RaspberryPi 4 ModelB.

Caused by: java.lang.IllegalStateException: Cannot find a suitable SQLite binary for Linux | aarch64. Please file a bug at https://issuetracker.google.com/issues/new?component=460784
        at androidx.sqlite.driver.bundled.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.jvm.kt:43)
        at androidx.sqlite.driver.bundled.BundledSQLiteDriver.<clinit>(BundledSQLiteDriver.jvmAndroid.kt:61)
        ... 49 more

Using sqlite-bundled as a dependency.

implementation("androidx.sqlite:sqlite-bundled:2.5.0-alpha04")

Apparently, only four types are currently supported: linux_x64, osx_arm64, osx_x64, and windows_x64.

As for the operating systems on which they are running, they are as follows:

$ uname -a
Linux pi 6.1.0-rpi7-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) aarch64 GNU/Linux

I would be very happy if you could support Linux aarch64 environment as well.

Comments

ap...@google.com <ap...@google.com> #2Aug 8, 2024 10:55AM

A couple of questions:

1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?

da...@google.com <da...@google.com> Aug 8, 2024 10:58AM

Marked as fixed.

me...@ralph.ms <me...@ralph.ms> #3Aug 8, 2024 03:32PM

Tested on Android 12 Emulator with custom executor, but cannot repro this issue.

na...@google.com <na...@google.com> #4Aug 21, 2024 07:55PM

Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
Dynamic features are not used in the application.

As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.

Issue 358045505

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2Aug 8, 2024 10:55AM

da...@google.com <da...@google.com> Aug 8, 2024 10:58AM

me...@ralph.ms <me...@ralph.ms> #3Aug 8, 2024 03:32PM

na...@google.com <na...@google.com> #4Aug 21, 2024 07:55PM

Add comment

Issue metadata