Assigned
Status Update
Comments
ad...@google.com <ad...@google.com>
ma...@google.com <ma...@google.com> #2
Fix should be a release of androidx.activity 1.3.0-alpha02 from build ab/7134643
ma...@google.com <ma...@google.com> #3
1.3.0-alpha02
Class 'androidx.activity.compose.ComponentActivityKt' is compiled by an unstable version of the Kotlin compiler and cannot be loaded by this compiler
Apps using Compose alpha12 and specifically artifacts like androidx.compose.ui:ui-test-junit4:1.0.0-alpha12
that internally use setContent
should add the activity-compose:1.3.0-alpha02
dependency to their dependencies
block to ensure that the 1.3.0-alpha01
artifact is not used:
implementation 'androidx.activity:activity-compose:1.3.0-alpha02'
sv...@google.com <sv...@google.com> #4
f
ma...@google.com <ma...@google.com> #5
Can I in script it manually or reset
sv...@google.com <sv...@google.com> #6
You simply need to update you app's build.gradle
to use:
implementation 'androidx.activity:activity-compose:1.3.0-alpha02'
instead of
implementation 'androidx.activity:activity-compose:1.3.0-alpha01'
je...@google.com <je...@google.com> #7
sv...@google.com <sv...@google.com> #8
Bonjour deliveroo s'il vous plaît j'aimerais absolument changer mon véhicule en vélo électrique. Mer
ap...@google.com <ap...@google.com> #10
Meine simcard fonktionirt nicht
ap...@google.com <ap...@google.com> #11
deleted
Description
Jetpack Compose version: 1.1.1 Jetpack Compose component used: LazyColumn Android Studio Build: Kotlin version: 1.6.10
When I use nestedScroll in this case, If the list can not scrll up, I expect to move LazyColumn self. So I use nestedScroll and offset. But I found that the velocity is negative sometimes when I scrolled up that should be positive.
I think it's because of offset change the LazyColumn's layout coordinates, but VelocityTracker does't know this, so touch position's coordinates collected by VelocityTracker are not same. This make the wrong velocity calculation.