Compose 1.8.0 alpha 3 broke fling [371168883]

Fixed

Bug

Status Update

No update yet.

Description

to...@gmail.com

created issue #1

Oct 3, 2024 02:55PM

Jetpack Compose version: Compose 1.8.0 alpha 3

Jetpack Compose component(s) used: Many

I'm not sure yet how to reproduce yet but see attached video.

The first screen is a Horizontal Lazy in a vertical one with snapfling.
On first display the fling works in both directions.
Scroll away then scrollback to redraw the Horizontal lazy then the fling does not work to right as you can see the overscroll effect runs all the time.

The second screen is an VerticalLazy on first display it can fling down but have the same issue when fling up.
Moving away then drawing away fixed this.

I can sometimes rarely, break the fling in the opposite direction on the first screen with the Horizontal one.

I'm a little puzzled by the difference between the screens when one works then don't work on redisplay, but the other is the opposite it first don't work then works.

Screen_recording_20241003_164949.mp4

24 MB

Download

Comments

to...@gmail.com <to...@gmail.com> #2Oct 3, 2024 02:58PM

Project: platform/frameworks/support
Branch: androidx-master-dev

commit b90079595f33f58fece04026a97faa0d243acdb1
Author: Yuichi Araki <yaraki@google.com>
Date: Wed Sep 18 16:55:49 2019

Change the way to detect mismatch between POJO and query

This fixes cursor mismatch warnings with expandProjection.

Bug: 140759491
Test: QueryMethodProcessorTest
Change-Id: I7659002e5e0d1ef60fc1af2a625c0c36da0664d8

M room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt
M room/compiler/src/test/kotlin/androidx/room/processor/QueryMethodProcessorTest.kt
M room/compiler/src/test/kotlin/androidx/room/testing/TestProcessor.kt

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

https://goto.google.com/android-sha1/b90079595f33f58fece04026a97faa0d243acdb1

le...@google.com <le...@google.com> #3Oct 3, 2024 03:04PM

The following changes were cherrypicked through Coastguard (

https://android-build.googleplex.com/coastguard/)
Release Track: (

https://android-build.googleplex.com/coastguard/dashboard/6093116828680192/#/cherrypickHistory/all)
Created: 2019-10-14 17:23:42.610596+00:00
Changes: aosp/1123258

to...@gmail.com <to...@gmail.com> #4Oct 3, 2024 03:07PM

Project: platform/frameworks/support
Branch: androidx-master-dev

commit bdde5a1a970ddc9007b28de4aa29d60ffa588f08
Author: Yigit Boyar <yboyar@google.com>
Date: Thu Apr 16 16:47:05 2020

Re-factor how errors are dismissed when query is re-written

This CL changes how we handle errors/warnings if query is
re-written.
There was a bug in expandProjection where we would report warnings
for things that Room already fixes automatically (

b/140759491

).
The solution to that problem (I7659002e5e0d1ef60fc1af2a625c0c36da0664d8)
solved it by deferring validating of columns until after re-write
decision is made. Unfortunately, this required changing PojoRowAdapter
to have a dummy mapping until it is validating, make it hard to use
as it does have a non-null mapping which is not useful.

This CL partially reverts that change and instead rely on the log
deferring logic we have in Context. This way, we don't need to break
the stability of PojoRowAdapter while still having the ability to
drop warnings that room fixes. This will also play nicer when we
have different query re-writing options that can use more information
about the query results.

Bug: 153387066
Bug: 140759491
Test: existing tests pass
Change-Id: I2ec967c763d33d7a3ff02c1a13c6953b460d1e5f

M room/compiler/src/main/kotlin/androidx/room/log/RLog.kt
M room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt

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

le...@google.com <le...@google.com> #5Oct 3, 2024 03:11PM

Reassigned to le...@google.com.

Yeah it should be mentioned in aosp/3260391. I'll update the release notes and work on a fix.

to...@gmail.com <to...@gmail.com> #6Oct 3, 2024 03:18PM

Thanks, for the record the second screen does not have nested scrolling directly it only have 2 nestedScroll modifiers that only override onPostScroll and always returns Offet.Zero

ap...@google.com <ap...@google.com> #7Oct 7, 2024 06:28PM

Marked as fixed.

Project: platform/frameworks/support
Branch: androidx-main
Author: Levi Albuquerque <levima@google.com>
Link: https://android-review.googlesource.com/3294571

Fix NestedScroll issue with onPostFling method.

Expand for full commit details

Fix NestedScroll issue with onPostFling method.

Fix NestedScroll issue with onPostFling method. We can use the NestedScrollDispatcher to cache the last known nested scroll parent and use that to dispatch the onPostFling event. We also need to make sure that the fling is cancelled when the scrollable node is detached to allow the propagation of nested scroll events.

Fixes: 303224944
Fixes: 371168883
Fixes: 371241898
Relnote: Introduce a fix for nested scrollbles that are removed from the node tree during an ongoing fling. Now these nodes will cancel the fling and correctly send the onPostFling event with the remaining velocity. We're also introducing the flag NewNestedScrollFlingDispatchingEnabled to control the behavior in case of regressions. The flag will be removed before beta.

Test: Added new tests for behavior.
Change-Id: I05c37b5d0ae42d8ed97c014383fe9df3282d61d6

Files:

M compose/foundation/foundation/integration-tests/lazy-tests/src/androidTest/kotlin/androidx/compose/foundation/lazy/list/LazyListTest.kt
M compose/foundation/foundation/src/androidInstrumentedTest/kotlin/androidx/compose/foundation/ScrollableTest.kt
M compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/ComposeFoundationFlags.kt
M compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/gestures/Scrollable.kt
M compose/ui/ui/api/current.txt
M compose/ui/ui/api/restricted_current.txt
M compose/ui/ui/src/androidInstrumentedTest/kotlin/androidx/compose/ui/input/nestedscroll/NestedScrollModifierTest.kt
M compose/ui/ui/src/commonMain/kotlin/androidx/compose/ui/ComposeUiFlags.kt
M compose/ui/ui/src/commonMain/kotlin/androidx/compose/ui/input/nestedscroll/NestedScrollModifier.kt
M compose/ui/ui/src/commonMain/kotlin/androidx/compose/ui/input/nestedscroll/NestedScrollNode.kt

Hash: 48c8610152dfb807c2c3dfa0a69ab0ec69e3bcfc
Date: Tue Sep 24 15:03:36 2024

to...@gmail.com <to...@gmail.com> #8Oct 8, 2024 10:22AM

Can confirm that after that commit the NewNestedFlingPropagationEnabled is no more needed and everything seems to work.

le...@google.com <le...@google.com> #9Oct 8, 2024 10:23AM

Thanks for confirming!

to...@gmail.com <to...@gmail.com> #10Oct 8, 2024 10:27AM

Thank for the fix.

Do you think this can also fix things like https://issuetracker.google.com/issues/353304855 ? And if not do you think you can have a look, it seems to be assigned to M3 team but it's complicated to get feedback and reactions from them.

na...@google.com <na...@google.com> #11Oct 16, 2024 05:48PM

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

androidx.compose.foundation:foundation:1.8.0-alpha04
androidx.compose.foundation:foundation-android:1.8.0-alpha04
androidx.compose.foundation:foundation-jvmstubs:1.8.0-alpha04
androidx.compose.ui:ui:1.8.0-alpha04
androidx.compose.ui:ui-android:1.8.0-alpha04
androidx.compose.ui:ui-jvmstubs:1.8.0-alpha04
androidx.compose.ui:ui-linuxx64stubs:1.8.0-alpha04