Fixed
Status Update
Comments
[Deleted User] <[Deleted User]> #2
With the change of lifecycle-common
to KMP, we might be able to just move this into the right spot (since it'll mirror the same structure as lifecycle-runtime
, which does work).
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #3
lifecycle-common
even after conversion to KMP is still a jar. We do not want to change that to an AAR as that is a breaking change for consumers, so i dont think we can make it work this project.
Description
Component used: Fragment Version used: 1.3.0 Devices/Android versions reproduced on: Android 10, 11
This is happen on our product code, but, sorry, I could not create sample project to reproduce this issue.
If we update fragment from 1.2.5 to 1.3.0, onResume is not called on one Fragment of our project. This is very similer to https://issuetracker.google.com/issues/177154873
Our Fragment has custom enter/exit transition. If we remove these custom transition, onResume is called as expected. But we can't do that. We need custom transition animation. The difference to above issue (177154873) may that our Fragment is "Fragment on Fragment".
We tried to call
https://medium.com/androiddevelopers/fragments-rebuilding-the-internals-61913f8bf48e
to disable new state manager.
FragmentManager.enableNewStateManager(false)
written inonResume becomes to be called !! BUT, it cause ConcurrentModificationException.
This is similar to following issues. https://issuetracker.google.com/issues/178460675
https://issuetracker.google.com/issues/152337205
But this is happen on 1.3.0.
Summary: