Fixed

Bug

Status Update

No update yet.

Description

ya...@gmail.com

created issue #1

May 20, 2024 09:45AM

Component used: androidx.room, androidx.sqlite:sqlite-bundled
Version used: androidx.room 2.7.0-alpha02, androidx.sqlite:sqlite-bundled 2.5.0-alpha02
Devices/Android versions reproduced on: Nexus 5X/8.1.0

I created an Android app using Room (Kotlin Multiplatform) and distributed it on the Play Store. Crashlytics reported that some Android devices were failing to instantiate the BundledSQLiteDriver.

Here is the stack trace.

      Fatal Exception: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "__atomic_store_4" referenced by "/data/app/com.example.myapp.androidApp-eZAPwaCuftjM0oTWOtQSJQ==/split_config.armeabi_v7a.apk!/lib/armeabi-v7a/libsqliteJni.so"...
       at java.lang.Runtime.loadLibrary0(Runtime.java:1071)
       at java.lang.Runtime.loadLibrary0(Runtime.java:1007)
       at java.lang.System.loadLibrary(System.java:1667)
       at androidx.sqlite.driver.bundled.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:24)
       at androidx.sqlite.driver.bundled.BundledSQLiteDriver.<clinit>(BundledSQLiteDriver.androidJvmCommon.kt:36)
       at com.example.myapp.shared.DataRepository.<init>(DataRepository.kt:39)
       at com.example.myapp.androidApp.MainApplication$appModule$1$3.invoke(MainApplication.java:144)
       at com.example.myapp.androidApp.MainApplication$appModule$1$3.invoke(MainApplication.java:143)
       at org.koin.core.instance.InstanceFactory.create(InstanceFactory.java:50)
       at org.koin.core.instance.SingleInstanceFactory.create(SingleInstanceFactory.java:46)
       at org.koin.core.instance.SingleInstanceFactory$get$1.invoke(SingleInstanceFactory.java:55)
       at org.koin.core.instance.SingleInstanceFactory$get$1.invoke(SingleInstanceFactory.java:53)
       at org.koin.mp.KoinPlatformTools.synchronized(KoinPlatformTools.java:36)
       at org.koin.core.instance.SingleInstanceFactory.get(SingleInstanceFactory.java:53)
       at org.koin.core.registry.InstanceRegistry.resolveInstance$koin_core(InstanceRegistry.java:109)
       at org.koin.core.scope.Scope.resolveValue(Scope.kt:247)
       at org.koin.core.scope.Scope.resolveInstance(Scope.kt:233)
       at org.koin.core.scope.Scope.get(Scope.kt:212)
       at com.example.myapp.shared.core.NovelPageReducer$special$$inlined$inject$default$6.invoke(NovelPageReducer.java:67)
       at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
       at com.example.myapp.shared.core.NovelPageReducer.getDataRepository(NovelPageCore.kt:153)
       at com.example.myapp.shared.core.NovelPageReducer.fetchIsBookmarked(NovelPageCore.kt:431)
       at com.example.myapp.shared.core.NovelPageReducer.access$fetchIsBookmarked(NovelPageCore.kt:143)
       at com.example.myapp.shared.core.NovelPageReducer$reduce$2.invokeSuspend(NovelPageCore.kt:176)
       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
       at android.os.Handler.handleCallback(Handler.java:883)
       at android.os.Handler.dispatchMessage(Handler.java:100)
       at android.os.Looper.loop(Looper.java:214)
       at android.app.ActivityThread.main(ActivityThread.java:7388)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:980)

I did not reproduce the above error on my Pixel 4a/Android 13.

Sample project to trigger the issue.

I created a sample project with a configuration similar to the production application where the error occurred.

https://github.com/k-yamada/ReproduceBundledSQLiteDriverError

Line where the error occurred.

https://github.com/k-yamada/ReproduceBundledSQLiteDriverError/blob/main/shared/src/commonMain/kotlin/com/example/reproduce/DataRepository.kt#L13

Devices with error reported by Crashlytics

V10/Android 10
Galaxy Feel/Android 8.0.0
Kfonwi/Android 9
Nexus 5X/Android 8.1.0
Tab M7 3rd Gen/Android 11
Pixel 3 XL/Android 9
Pixel 6 Pro/Android 12
K10C/Android 13
FFFTAB8/Android 12

Comments

da...@google.com <da...@google.com> #2May 21, 2024 07:45AM

First of all thanks for this detailed issue.

This issue had been investigated thoroughly when it was first reported internally. The surprising detail in this report is that the issue is not reproducible before 1.7. I will look into this.

The main problem with POBox is the fact that it is deprecated. Since 2021 Sony has been shipping new Xperia devices with Gboard pre-installed. Although we are aware that there is still a considerable amount of users still using POBox, the described behavior is caused by POBox's noncompliant behavior with InputConnection and InputMethodManager documentation. However, this is understandable since TextView implementation was also not respecting the behavior that is expected from Editors.

Ultimately we have decided to enforce the documented behavior with specifically regards to when editors should call InputMethodManager.updateSelection. Also, although unconfirmed, there were traces of possible custom code being included in Sony OEM images that changed how InputMethodManager was notified from TextView. If POBox also depended on something like this, it would be impossible for Compose code to replicate the same unknown behavior.

da...@google.com <da...@google.com> #3May 21, 2024 09:50AM

If the investigation takes time, would it be possible to revert the surrounding implementation to 1.6.x equivalent?

Or is that option not available?

Even if the root cause is POBox, from the perspective of the app's customers, it looks like an app bug, so this issue is a blocker against updating Jetpack Compose.

ad...@ally.rapido.bike <ad...@ally.rapido.bike> #4May 29, 2024 08:42AM

Just to be sure, it is dangerous to replace Compose TextField with Android View EditText as a workaround for this issue.

Compose 1.7 has a bug that causes ANR when the focus is on EditText. https://issuetracker.google.com/issues/369354336

Another View-related bug in Compose 1.7 is that an Android View is focused by calling FocusManager.clearFocus(). https://issuetracker.google.com/issues/374031296

Perhaps there is a lack of testing of Compose 1.7 in combination with Android View. There is also a possibility that there are other fatal bugs related to View.

In other words, the only options for apps targeting the Japanese market that require POBox support are to continue using Compose 1.6 or to use EditText in combination with various workarounds.

ap...@google.com <ap...@google.com> #5May 30, 2024 01:07AM

Project: platform/frameworks/support
Branch: androidx-main
Author: Halil Ozercan <halilibo@google.com>
Link: https://android-review.googlesource.com/3317256

Fix POBox keyboard issue

Expand for full commit details

Fix POBox keyboard issue 
 
Fix: 373743376 
Fix: 329209241 
Test: NullableInputConnectionWrapperTest 
Change-Id: I94e0e598274fb88b255f977f9fbd50dfbbb1ecb1

Files:

M compose/ui/ui/src/androidInstrumentedTest/kotlin/androidx/compose/ui/text/input/NullableInputConnectionWrapperTest.kt
M compose/ui/ui/src/androidMain/kotlin/androidx/compose/ui/text/input/NullableInputConnectionWrapper.android.kt

Hash: 57f58c4b80d5d8470b2aca325dfdcd55f235231e
Date: Thu Oct 24 01:25:20 2024

da...@google.com <da...@google.com> May 30, 2024 01:09AM

Marked as fixed.

bo...@gmail.com <bo...@gmail.com> #6Jun 25, 2024 12:42PM

Many thanks again for this report. Especially for giving us a huge clue in terms of what could be going wrong. The fix is now merged and I will ask for a cherry-pick into a stable release.

da...@google.com <da...@google.com> #7Jun 25, 2024 12:45PM

Thank you for fixing the issue, I confirmed the fix was released in version 1.8.0-alpha05.
Do you have any concrete plan to cherry-pick the fix into current stable version (1.7.x)? We are currently waiting it.

bo...@gmail.com <bo...@gmail.com> #8Jun 25, 2024 01:10PM

Yes, this fix is planned to be included in a future 1.7.x release.

da...@google.com <da...@google.com> #9Jun 25, 2024 01:17PM

Thanks for the fix. Sorry to follow up on this. is it possible for you to share specific release version/date for the stable version? We are waiting on this to decide on our direction.

ro...@gmail.com <ro...@gmail.com> #10Aug 16, 2024 02:09PM

I believe this error still exists.

I just received two errors from Crashlytics using androidx.sqlite:sqlite-bundled version 2.5.0-alpha06 and BundledSQLiteDriver for both Android and iOS.

Fatal Exception: java.lang.UnsatisfiedLinkError
dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/app/com.example.app-ACdqnxIlCwzIlzMdaeegRw==/base.apk"],nativeLibraryDirectories=[/data/app/com.example.app-ACdqnxIlCwzIlzMdaeegRw==/lib/x86, /system/lib, /vendor/lib]]] couldn't find "libsqliteJni.so"

And the exception is in .setDriver(BundledSQLiteDriver())

Both crashes were from a Nexus 5X running Android 8.1.0

I would say it is the same exception as in

comment #6

ev...@due.network <ev...@due.network> #11Oct 31, 2024 12:19PM

Same crash on Nexus 5X running Android 8.1.0 on androidx.sqlite:sqlite-bundled version 2.5.0-alpha10 with room version 2.7.0-alpha10.

f2...@gmail.com <f2...@gmail.com> #12Nov 9, 2024 03:14AM

Same crash on Pixel 6 Pro(android12),Nexus 5X(android8.1) on androidx.sqlite:sqlite-bundled version 2.5.0-alpha11 with room version 2.7.0-alpha11.

ke...@level.co <ke...@level.co> #13Nov 14, 2024 04:30PM

Same crash on Android 12, Pixel 6 Pro.
androidx.sqlite:sqlite-bundled version 2.5.0-alpha11 with room version 2.7.0-alpha11

da...@google.com <da...@google.com> #14Nov 14, 2024 11:11PM

For those experiencing this issue, can you provide any more detail: stacktrace, bug report, trends (specific API versions, specific manufacturer)?

Usually with UnsatisfiedLinkError there is more in the logs / error mentioning why the native library couldn't be used, specifically the missing symbol. I have so far validated we are linking against the right atomic library in the NDK, so I suspect it must be another symbol.

ki...@protonmail.com <ki...@protonmail.com> #15Dec 8, 2024 10:12PM

Same crash on Pixel 6 pro

androidx-room = "2.7.0-alpha11"

androidx-sqlite = "2.5.0-alpha11"

Attached a stack trace

Message last modified on Dec 8, 2024 10:13PM

0a349c077202524f96de843fde217909_crash_session_675378B4004800010C938EC151423BF4_DNE_0_v2_stacktrace.txt

34 KB

View

Download

da...@nutrium.com <da...@nutrium.com> #16Dec 11, 2024 10:04AM

Hi, we released a app yesterday and we are facing the same issue with the same stack trace of

https://issuetracker.google.com/issues/341639198#comment15

Does anyone knows if it's safe to use AndroidSQLiteDriver for android as a backup plan?

We also released the iOS app some weeks ago and until know we didn't catch any issue related to this.

da...@google.com <da...@google.com> #17Dec 11, 2024 04:32PM

For the stacktrace in comment#15 its as if the JNI lib was not packaged with the APK, can you confirm if the APK has the native libraries? They should be located in jni/<abi>/libsqliteJni.so

da...@nutrium.com <da...@nutrium.com> #18Dec 18, 2024 03:28PM

Hi, thanks for the reply we don't have the JNI lib jni/<abi>/libsqliteJni.so
We have the structure like in the screenshoot

Screenshot 2024-12-18 at 15.23.44.png

54 KB

View

Download

al...@gmail.com <al...@gmail.com> #19Dec 28, 2024 01:47PM

Facing the same

issue 2

.7.0-alpha12

IssueTracker

BundledSQLiteDriver: couldn't find "libsqliteJni.so"

Status Update

Description

Sample project to trigger the issue.

Devices with error reported by Crashlytics

Comments

da...@google.com <da...@google.com> #2May 21, 2024 07:45AM

da...@google.com <da...@google.com> #3May 21, 2024 09:50AM

ad...@ally.rapido.bike <ad...@ally.rapido.bike> #4May 29, 2024 08:42AM

ap...@google.com <ap...@google.com> #5May 30, 2024 01:07AM

da...@google.com <da...@google.com> May 30, 2024 01:09AM

bo...@gmail.com <bo...@gmail.com> #6Jun 25, 2024 12:42PM

da...@google.com <da...@google.com> #7Jun 25, 2024 12:45PM

bo...@gmail.com <bo...@gmail.com> #8Jun 25, 2024 01:10PM

da...@google.com <da...@google.com> #9Jun 25, 2024 01:17PM

ro...@gmail.com <ro...@gmail.com> #10Aug 16, 2024 02:09PM

ev...@due.network <ev...@due.network> #11Oct 31, 2024 12:19PM

f2...@gmail.com <f2...@gmail.com> #12Nov 9, 2024 03:14AM

ke...@level.co <ke...@level.co> #13Nov 14, 2024 04:30PM

da...@google.com <da...@google.com> #14Nov 14, 2024 11:11PM

ki...@protonmail.com <ki...@protonmail.com> #15Dec 8, 2024 10:12PM

da...@nutrium.com <da...@nutrium.com> #16Dec 11, 2024 10:04AM

da...@google.com <da...@google.com> #17Dec 11, 2024 04:32PM

da...@nutrium.com <da...@nutrium.com> #18Dec 18, 2024 03:28PM

al...@gmail.com <al...@gmail.com> #19Dec 28, 2024 01:47PM

Issue 341639198

Description

Sample project to trigger the issue.

Devices with error reported by Crashlytics

Issue summary

Comments

da...@google.com <da...@google.com> #2May 21, 2024 07:45AM

da...@google.com <da...@google.com> #3May 21, 2024 09:50AM

ad...@ally.rapido.bike <ad...@ally.rapido.bike> #4May 29, 2024 08:42AM

ap...@google.com <ap...@google.com> #5May 30, 2024 01:07AM

da...@google.com <da...@google.com> May 30, 2024 01:09AM

bo...@gmail.com <bo...@gmail.com> #6Jun 25, 2024 12:42PM

da...@google.com <da...@google.com> #7Jun 25, 2024 12:45PM

bo...@gmail.com <bo...@gmail.com> #8Jun 25, 2024 01:10PM

da...@google.com <da...@google.com> #9Jun 25, 2024 01:17PM

ro...@gmail.com <ro...@gmail.com> #10Aug 16, 2024 02:09PM

ev...@due.network <ev...@due.network> #11Oct 31, 2024 12:19PM

f2...@gmail.com <f2...@gmail.com> #12Nov 9, 2024 03:14AM

ke...@level.co <ke...@level.co> #13Nov 14, 2024 04:30PM

da...@google.com <da...@google.com> #14Nov 14, 2024 11:11PM

ki...@protonmail.com <ki...@protonmail.com> #15Dec 8, 2024 10:12PM

da...@nutrium.com <da...@nutrium.com> #16Dec 11, 2024 10:04AM

da...@google.com <da...@google.com> #17Dec 11, 2024 04:32PM

da...@nutrium.com <da...@nutrium.com> #18Dec 18, 2024 03:28PM

al...@gmail.com <al...@gmail.com> #19Dec 28, 2024 01:47PM

Add comment

Issue metadata