Fixed
Status Update
Comments
il...@google.com <il...@google.com>
mg...@google.com <mg...@google.com>
ap...@google.com <ap...@google.com> #2
Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue.
il...@google.com <il...@google.com>
pr...@google.com <pr...@google.com> #3
My chroming bug
he...@reaktor.com <he...@reaktor.com> #4
We’d appreciate any update or timeline for fixing this issue.
I currently blocks any debugging on x86_64 emulators using Qt (seehttps://bugreports.qt.io/browse/QTBUG-77113 ).
Thanks!
I currently blocks any debugging on x86_64 emulators using Qt (see
Thanks!
il...@google.com <il...@google.com> #5
Allow I dont know what it all is
ha...@gmail.com <ha...@gmail.com> #6
Feedback
Description
When using Compose navigation, calls to navigate should be guarded by lifecycle state to prevent invoking navigation methods while composable is transitioning as an effect of navigation. Given navigation destination:
navigation calls should be guarded by
backStackEntry
lifecycle state to prevent invoking navigation from composable that's under transition:It would be really useful to have a set of lifecycle aware function wrappers for guarding execution of calls, for example:
or standalone composable version which will use
LocalLifecycleOwner
to access lifecycle state: