Status Update
No update yet.
Comments
mo...@google.com
Does the program work without the compiler switch. That is, is `"-P", "plugin:androidx.compose.compiler.plugins.kotlin:experimentalStrongSkipping=true",` required to reproduce or is just changing the runtime enough?
mo...@google.com
Sorry for that, I will try to extract an example when I'm free.
ap...@google.com
I have find a sample code to reproduce that
setContent {
val dialogState = remember { DialogState() }
dialogState.Intercept()
LaunchedEffect(Unit) {
delay(1000)
dialogState.bgWork {
delay(5000)
}
dialogState.showSelectActions {
onSelect("a") {
}
onSelect("b") {
}
}
}
}
You can find implementation of DialogState here
na...@google.com
Let me sort it out
The first crash
Reproduce: navigate to a gallery and navigate back
The reason is we have some code assume the forget order of RememberObserver(DisposableEffect), and 52835066c9044647a65dfb566f03131aab46e793 changed the order. Seems this is a intended behaviour.
I will fix it from my side. My bad
The second crash
Reproduce: #4 comment
StackTrace:
We got a wrong object from SlotTable during recompose
Description
Version used: 1.5.0-alpha01
Devices/Android versions reproduced on: API 34 device
When doing a Slide transition with Transition version `1.5.0-alpha01`, if you interrupt the transition the exiting View will jump a few pixels before sliding to the proper exit location creating an undesired effect. I am using a horizontal (Gravity.START) so it is unclear why the View would change vertically at all.
To reproduce, launch the app and click the next button and right before the transition completes, press it again.
I would expect that behavior to be consistent with what was in previous version which is no jump, and the transition smoothly reversing.