SearchView in Activity is collapsing after DialogFragment is dismissed [244336571]

Fixed

Bug

Status Update

No update yet.

Description

me...@gmail.com

created issue #1

Aug 30, 2022 09:46PM

Component used: Fragment

Version used: 1.5.2

Devices/Android versions reproduced on: Android 12

I'm using SearchView in my Activity. If SearchView is expanded and i'm opening DialogFragment on the top of the activity and then dismissing it, SearchView is being collapsed. It must not collapse.
Seems like some bug in Fragment 1.5.0 - 1.5.2 version. In 1.4.1 version everything is working fine.

Please suggest some workarounds or how to fix this issue?

Comments

il...@google.com <il...@google.com> #2Aug 30, 2022 09:56PM

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.

me...@gmail.com <me...@gmail.com> #3Sep 1, 2022 07:18AM

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

sample_project.zip

107 KB

Download

me...@gmail.com <me...@gmail.com> #4Sep 6, 2022 07:16AM

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

lb...@gmail.com <lb...@gmail.com> #5Sep 6, 2022 06:34PM

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

me...@gmail.com <me...@gmail.com> #6Sep 26, 2022 08:48AM

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!

il...@google.com <il...@google.com> Sep 28, 2022 10:01PM

Assigned to jb...@google.com.

mi...@gmail.com <mi...@gmail.com> #7Oct 10, 2022 07:47PM

Can you try using androidx.room:room-runtime-android:2.7.0-alpha04 and confirm if the issue is still present?

lb...@gmail.com <lb...@gmail.com> #8Oct 10, 2022 08:36PM

I will let you know, in alternative can I use AndroidSQLiteDriver instead of the bundled one just for the android implementation?

ab...@gmail.com <ab...@gmail.com> #9Oct 13, 2022 05:32AM

Ideally you could use AndroidSQLiteDriver but Room has a bug with the AndroidSQLiteDriver that is fixed in version 2.7.0-alpha05 that will be released in July 10 so I recommend that if you do switch to using AndroidSQLiteDriver wait for the alpha05 release.

me...@gmail.com <me...@gmail.com> #10Nov 3, 2022 03:34PM

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

ab...@gmail.com <ab...@gmail.com> #11Feb 6, 2023 07:37AM

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.

lb...@gmail.com <lb...@gmail.com> #12Feb 6, 2023 11:39AM

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.

jb...@google.com <jb...@google.com> Feb 7, 2023 05:53PM

Reassigned to sa...@google.com.

sa...@google.com <sa...@google.com> Feb 17, 2023 05:11AM

Accepted by sa...@google.com.

ap...@google.com <ap...@google.com> #13Mar 2, 2023 06:22PM

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

sa...@google.com <sa...@google.com> Mar 2, 2023 06:54PM

Marked as fixed.

lb...@gmail.com <lb...@gmail.com> #14Mar 2, 2023 07:32PM

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.

jb...@google.com <jb...@google.com> #15Mar 2, 2023 07:47PM

Same crash on Pixel 6 pro

androidx-room = "2.7.0-alpha11"

androidx-sqlite = "2.5.0-alpha11"

Attached a stack trace

lb...@gmail.com <lb...@gmail.com> #16Mar 2, 2023 07:55PM

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.

na...@google.com <na...@google.com> #17Mar 8, 2023 07:51PM

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

lb...@gmail.com <lb...@gmail.com> #18Mar 8, 2023 08:08PM

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

lb...@gmail.com <lb...@gmail.com> #19Mar 8, 2023 08:37PM

Facing the same

issue 2

.7.0-alpha12

studio64_2023-03-08_22-35-27.mp4

18 MB

Download

My Application.zip

113 KB

Download

pr...@google.com <pr...@google.com> #20Mar 22, 2023 08:24PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.fragment:fragment:1.5.6

lb...@gmail.com <lb...@gmail.com> #21Mar 22, 2023 09:01PM

@20 Not 1.6.0-alpha07 ?

th...@gmail.com <th...@gmail.com> #22Mar 24, 2023 06:46PM

@21 androidx.fragment:fragment:1.5.6 is a STABLE release. It has the fix we need. The androidx.fragment:fragment:1.6.0-alpha07 is an alpha as it says. 1.6 is "work in progress". 1.6.0 is still not a stable release. Use "alpha" only for testing

lb...@gmail.com <lb...@gmail.com> #23Mar 24, 2023 09:28PM

@22 So it's fixed on both. OK

Issue 244336571

Description

Issue summary

Comments

il...@google.com <il...@google.com> #2Aug 30, 2022 09:56PM

me...@gmail.com <me...@gmail.com> #3Sep 1, 2022 07:18AM

me...@gmail.com <me...@gmail.com> #4Sep 6, 2022 07:16AM

lb...@gmail.com <lb...@gmail.com> #5Sep 6, 2022 06:34PM

me...@gmail.com <me...@gmail.com> #6Sep 26, 2022 08:48AM

il...@google.com <il...@google.com> Sep 28, 2022 10:01PM

mi...@gmail.com <mi...@gmail.com> #7Oct 10, 2022 07:47PM

lb...@gmail.com <lb...@gmail.com> #8Oct 10, 2022 08:36PM

ab...@gmail.com <ab...@gmail.com> #9Oct 13, 2022 05:32AM

me...@gmail.com <me...@gmail.com> #10Nov 3, 2022 03:34PM

ab...@gmail.com <ab...@gmail.com> #11Feb 6, 2023 07:37AM

lb...@gmail.com <lb...@gmail.com> #12Feb 6, 2023 11:39AM

jb...@google.com <jb...@google.com> Feb 7, 2023 05:53PM

sa...@google.com <sa...@google.com> Feb 17, 2023 05:11AM

ap...@google.com <ap...@google.com> #13Mar 2, 2023 06:22PM

sa...@google.com <sa...@google.com> Mar 2, 2023 06:54PM

lb...@gmail.com <lb...@gmail.com> #14Mar 2, 2023 07:32PM

jb...@google.com <jb...@google.com> #15Mar 2, 2023 07:47PM

lb...@gmail.com <lb...@gmail.com> #16Mar 2, 2023 07:55PM

na...@google.com <na...@google.com> #17Mar 8, 2023 07:51PM

lb...@gmail.com <lb...@gmail.com> #18Mar 8, 2023 08:08PM

lb...@gmail.com <lb...@gmail.com> #19Mar 8, 2023 08:37PM

pr...@google.com <pr...@google.com> #20Mar 22, 2023 08:24PM

lb...@gmail.com <lb...@gmail.com> #21Mar 22, 2023 09:01PM

th...@gmail.com <th...@gmail.com> #22Mar 24, 2023 06:46PM

lb...@gmail.com <lb...@gmail.com> #23Mar 24, 2023 09:28PM

Add comment

Issue metadata