Fixed
Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
Can you rise priority please?
It's a real stopper to use in not helloworld apps.
It must be joke, define it as "An issue that should be addressed eventually. Such an issue is not relevant to core organizational functions or the work of other teams, or else it relates only to the attractiveness or pleasantness of the system."
Why use compose in production, if this base things resolved for years?
It's a real stopper to use in not helloworld apps.
It must be joke, define it as "An issue that should be addressed eventually. Such an issue is not relevant to core organizational functions or the work of other teams, or else it relates only to the attractiveness or pleasantness of the system."
Why use compose in production, if this base things resolved for years?
il...@google.com
This is high priority for us. The "Priority" field on buganizer is misleading, it has a very specific internal meaning and interaction with other systems so we don't use it for actual prioritization for compose text issues. Unfortunately, the way we track actual priority is not visible externally.
Description
Component used: Fragment Version used: 1.3.0-alpha08
If you do:
The view is still present in the layout hierarchy even though the fragment did go through
onDestoryView().Bug doesn't happen if you call
FragmentManager.enableNewStateManager(false).sample project:https://github.com/evant/fragment-view-issue