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

Indexing also runs indefinitely here with Android studio 3.3 and a project that contains a NDK library (native engine + game). Previous versions, for instance 3.2.1, worked fine. Still occurs after clearing the caches and deleting the .idea folder. On a desktop with 32 GB of RAM it's not running out of memory but it indexes forever, pegging an entire CPU and disk access to 100%, and it never stops. The same thing occurs with gradle 4.6 or 4.10. If I enable the experimental scan active configuration only setting, everything is basically broken - no syntax highlighting, cpp files don't show. Waiting to see if there's a workaround before reverting to 3.2.1 and being much more cautious about updating in the future ..

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

When I let it run for hours, the scanning eventually did complete, then the indexing took more hours, I let it run as well, and eventually it switched to 'building symbols' which also started taking a long time without progress, but that, eventually, crashed Android Studio with an out of memory error, telling me to increase the heap size. I did, and upon restarting Android Studio, it started over at scanning .. so I gave up for now. This is with a mid-size NDK project.

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

Even after a dirty downgrade to AS 3.2 from 3.3 my project was stuck on scanning files to index and building symbols. I ended up having to fully remove all Android Studio files/folders. After relaunching AS 3.2 and setting heap size to 8GB the scanning, indexing and building symbols took just a couple minutes.

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