Fixed
Status Update
Comments
il...@google.com <il...@google.com>
hu...@google.com <hu...@google.com>
[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>
ap...@google.com <ap...@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().
il...@google.com <il...@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).
Description
Version used: 1.2.0-alpha02
I can't use fragment-testing 1.2.0-x or 1.1.0-x with the latest espresso release (3.2.0) because of a strict depedency on androidx.test:core:1.1.0.
This is the error message from gradle:
Cannot find a version of 'androidx.test:core' that satisfies the version constraints:
Dependency path 'myappname:app:unspecified' --> 'androidx.test.espresso:espresso-intents:3.2.0' --> 'androidx.test:core:1.2.0'
Constraint path 'myappname:app:unspecified' --> 'androidx.test:core:{strictly 1.1.0}' because of the following reason: debugRuntimeClasspath uses version 1.1.0
Dependency path 'myappname:app:unspecified' --> 'androidx.fragment:fragment-testing:1.2.0-alpha02' --> 'androidx.test:core:1.1.0'