Status Update
Comments
ap...@google.com <ap...@google.com> #2
Hi, thanks for reporting this. Please update this ticket with a reproducible code/sample so we can better investigate the issue.
Thanks!
mg...@google.com <mg...@google.com>
il...@google.com <il...@google.com> #3
The endless joy of support tracker ....
So I'm actually asking a question ... So instead of insta closing without reading anyway to have someone read and answer?
What / Where are the settings that controls the velocity calculations.
Compose animations are tied to Android dev settings animation scale. What is the equivalent here.
pr...@google.com <pr...@google.com> #4
Not all compose animations are tied to Android developer settings.
Fling animations in lists are no longer controlled by the Settings menu and cannot be overriden, so that shouldn't be source of the problem you're seeing. This has been solved in
The velocity calculation for lists is done at the draggable level and are also transparent to developers, so you cannot control how these are calculated.
A sample/reproducible code is required if I was to move forward with investigating this issue.
Description
Currently, Lifecycle.eventFlow stops sending out new events when the
Lifecycle
reaches theDESTROYED
state. However, theFlow
never completes.Ideally, Lifecycle.eventFlow should complete when the
Lifecycle
isDESTROYED
. This would signal to consumers that they won't receive any new emissions and the flow is terminated.We found this issue while working on b/370577987 , which disallows moving from the
DESTROYED
state to any other state.