Fixed
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
Jeremy, is this still an issue? I think the problem was that you had two transitions targeting the same View for the same action (e.g. two Slide() transitions).
il...@google.com
ap...@google.com
I have a similar issue with plain AnimatorSet:
set.start()
set.pause()
set.setCurrentPlayTime(100)
set.setCurrentPlayTime(0)
set.setCurrentPlayTime(100)
set.resume()
doesn't play animation in resume().
jb...@google.com
Should clarify that if I filter out setCurrentPlayTime(0) (or replace it with setCurrentPlayTime(1)) it works well.
Also even with setCurrentPlayTime(0), onAnimationEnd is notified with correct delay (as if the animation has played).
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
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.
But this is happen on 1.3.0.
Summary: