Fixed
Status Update
Comments
[Deleted User] <[Deleted User]> #2
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 <il...@google.com>
jb...@google.com <jb...@google.com> #3
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().
ap...@google.com <ap...@google.com> #4
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).
jb...@google.com <jb...@google.com> #5
@
I think that is intended for Animator. If you set the currentPlayTime
to 0 or the total duration the animator completes. We do some
Description
Version used: androidx.fragment:fragment-ktx:1.3.3
Devices/Android versions reproduced on: Google Pixel API 29
I've noticed that reveal animation on view outside fragment container not working on 1.3.3, when fragment container contains bottom nav (see videos).
It seems like an inset dispatching problem, cause logs shows a lot of useless inset events on reveal target view (see screenshots).
Test project also attached.