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

Project: platform/frameworks/support
Branch: androidx-main

commit c73bd92631a2ff341f89001bc9143c7b998333e8
Author: Sanura N'Jaka <sanura@google.com>
Date: Thu Aug 18 18:03:13 2022

Add project dependency constraint between lifecycle-viewmodel and lifecycle-viewmodel-savedstate

Added bi-directional project version constraint between
lifecycle-viewmodel and lifecycle-viewmodel-savedstate.
If both artifacts are in the dependency tree, their
versions should match. This will now be enforced by gradle
automatically bumping up either version to meet constraint.

Test: N/A
Bug: 242871265
Change-Id: I3ab2abf9b6b1861038afc0e651da80e4ee75efb8

M lifecycle/lifecycle-viewmodel-savedstate/build.gradle

https://android-review.googlesource.com/2189976

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

Project: platform/frameworks/support
Branch: androidx-main

commit e7a81dc92c9c56b31455c75161a8becf49f761e3
Author: Sanura N'Jaka <sanura@google.com>
Date: Wed Aug 17 22:44:55 2022

Add project dependency constraint between lifecycle-runtime and lifecycle-runtime-compose

Added bi-directional project version constraint between
lifecycle-runtime and lifecycle-runtime-compose. If both
artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle
automatically bumping up either version to meet constraint.

Test: N/A
Bug: 242871265
Change-Id: I0f6b3928ac0b338b0fcc6835828dd43fadee8c0d

M lifecycle/lifecycle-runtime-compose/build.gradle
M lifecycle/lifecycle-runtime/build.gradle

https://android-review.googlesource.com/2189951

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

Project: platform/frameworks/support
Branch: androidx-main

commit b671082b2d2ba47ca41f33646780e797ac6689cc
Author: Sanura N'Jaka <sanura@google.com>
Date: Wed Aug 17 20:02:11 2022

Add project dependency constraint between lifecycle-common and lifecycle-runtime

Added bi-directional project version constraint between lifecycle-common and
lifecycle-runtime. If both artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle automatically bumping up
either version to meet constraint.

Test: N/A
Bug: 242871265
Change-Id: I98fea6d1a6b2cde61b0cf5c7822cd98b6218c578

M lifecycle/lifecycle-runtime/build.gradle
M lifecycle/lifecycle-common/build.gradle

https://android-review.googlesource.com/2188999

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