Locations sent to one emulator are sent to all of them [73450633]

Fixed

Bug

Status Update

No update yet.

Description

bo...@gmail.com

created issue #1

Feb 16, 2018 05:51PM

Android Studio Version:

Emulator Version (Emulator--> Extended Controls--> Emulator Version): 27.1.7-4581633

HAXM / KVM Version: HVF 10.13.0

Android SDK Tools: 26.1.1

Host Operating System: Mac OS X 10.13.3

CPU Manufacturer: Intel CPU
Virtualization is supported
64-bit CPU

Steps to Reproduce Bug:
- Open 2 emulators
- In one of them, send a location, using Extended controls / Location

Expected Behavior:
The location should be sent only to the emulator that was used.

Observed Behavior:
The location is sent to both emulators.

Because of this, tests involving two people interacting at two different locations are almost impossible to do.

Comments

lf...@google.com <lf...@google.com> Feb 17, 2018 12:13AM

Assigned to lf...@google.com.

lf...@google.com <lf...@google.com> #2Feb 18, 2018 03:48AM

Thanks for trying out Room KMP! This looks like an issue with Android 9+ and armv7 and the way we compile sqlite3.c, specifically linking to the atomic library in C. We'll try to get this fix as soon as possible.

ap...@google.com <ap...@google.com> #3Feb 20, 2018 09:36PM

Very related: https://sqlite.org/forum/info/aa703e86823efca3, as suspected seems like a linking issue.

ap...@google.com <ap...@google.com> #4Feb 20, 2018 09:41PM

Facing the same issue here, surprisingly using the AndroidSQLiteDriver instead of the bundled one seems to work fine. So for now, others facing the crash can fix it by using the AndroidSQLiteDriver instead of the bundled one

pj...@google.com <pj...@google.com> Feb 21, 2018 06:25PM

Marked as fixed.

lf...@google.com <lf...@google.com> #5Feb 21, 2018 06:39PM

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

commit cf121571aac008a756b64cda13f76ae4db3e85a6
Author: Daniel Santiago Rivera <danysantiago@google.com>
Date: Wed May 29 11:14:42 2024

Link to Android's atomic lib in bundled SQLite

Fix Bundled SQLite loading for devices with older ARM architecture by linking to Android's atomic library instead of relying on Clang's extension (c_atomic) or GCC's built-ins as used in sqlite3.c.

Also add support for passing linker args to androidx's native compilation infra.

See also discussion in

https://sqlite.org/forum/forumpost/792d76a592608d8f

Bug: 341639198
Test: Locally tested via BundledSQLiteDriverTest in a Nexus 5 on API 23
Change-Id: Ia818b7c4f1a990a1b5e35f4c7a3c89694aee0503

M buildSrc/private/src/main/kotlin/androidx/build/clang/ClangSharedLibraryTask.kt
M buildSrc/private/src/main/kotlin/androidx/build/clang/KonanBuildService.kt
M buildSrc/private/src/main/kotlin/androidx/build/clang/MultiTargetNativeCompilation.kt
M buildSrc/private/src/main/kotlin/androidx/build/clang/NativeTargetCompilation.kt
M sqlite/sqlite-bundled/build.gradle

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

lf...@google.com <lf...@google.com> #6Feb 24, 2018 06:14AM

Hello, even if I updated to version androidx.sqlite:sqlite-bundled:2.5.0-alpha04 I just received a crash on a nexus 5X with android 8.1.0 and another one on Redmi Note 11 Pro with android 13.
I'm using androidx.room:room-runtime-android:2.7.0-alpha01.

This is the log:
Fatal Exception: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.myproject-ssibkzVuLAo7tvV0puYoEg==/base.apk"],nativeLibraryDirectories=[/data/app/com.myproject-ssibkzVuLAo7tvV0puYoEg==/lib/x86, /system/lib, /vendor/lib]]] couldn't find "libsqliteJni.so"
at java.lang.Runtime.loadLibrary0(Runtime.java:1011)
at java.lang.System.loadLibrary(System.java:1657)
at androidx.sqlite.driver.bundled.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.android.kt:1)
at androidx.sqlite.driver.bundled.BundledSQLiteDriver.<clinit>(BundledSQLiteDriver.jvmAndroid.kt:1)

Thank you!