AnchoredDraggableState does not update progress when re-anchoring [294991954]

Fixed

Bug

Status Update

No update yet.

Description

da...@google.com

created issue #1

Aug 8, 2023 01:47PM

Jetpack Compose version: androidx.compose.foundation:foundation:1.6.0-alpha02

Jetpack Compose component(s) used: AnchoredDraggableState

Android Studio Build: Giraffe

Kotlin version: 1.8.10

Steps to Reproduce or Code Sample to Reproduce:

The progress property in AnchoredDraggable state does not update when re-anchoring; it only updates during user interaction.

    LaunchedEffect(state.progress) {
        println("progress: ${state.progress}")
    }

In the snippet above, progress will only update when dragging a widget with the modifier applied. Once draging stops and reanchoring begins to the nearest anchor, the progress value does not update until the Composable has snapped back and settled.

This makes it impossible to animate smoothly as the progress snaps to the the end value instead of being updated continuously.

Comments

jo...@google.com <jo...@google.com> #2Aug 8, 2023 02:14PM

Reassigned to jo...@google.com.

A couple of questions:

1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?

da...@google.com <da...@google.com> #3Aug 8, 2023 02:17PM

Tested on Android 12 Emulator with custom executor, but cannot repro this issue.

jo...@google.com <jo...@google.com> #4Mar 4, 2024 04:55PM

Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
Dynamic features are not used in the application.

As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.

ap...@google.com <ap...@google.com> #5Mar 5, 2024 12:30PM

Hmm, I feel the crash might be something related to separate/secondary process.

I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.

ap...@google.com <ap...@google.com> #6Mar 8, 2024 01:20PM

On the contrary, there was no separate process before, when crashes started.

In the new build (with the aforementioned changes) I can see SIGSEGV crash, but only one instead of dozens and it has a bit different backtrace:

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
liblanguage_id_jni.so (offset 0x11e000)

backtrace:
  #00  pc 000000000003c7c0  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 000000000003b960  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 000000000003bb48  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 000000000003bafc  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000036c98  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000032714  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000031cac  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000057438  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/oat/arm64/base.odex (offset 0x57000)

jo...@google.com <jo...@google.com> Mar 21, 2024 04:05PM

Marked as fixed.

Issue 294991954