Fixed
Status Update
No update yet.
Comments
il...@google.com
jh...@themeetgroup.com
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).
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().
fr...@google.com
an...@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).
sa...@peilicke.de
@
I think that is intended for Animator. If you set the currentPlayTime to 0 or the total duration the animator completes. We do some
po...@gmail.com
Comment has been deleted.
Description
Version used: 1.1.0 (and most others)
Devices/Android versions reproduced on: N/A
The logical way that a developer would choose to add fragment-testing into the androidTest configuration is with:
androidTestImplementation "androidx.fragment:fragment-testing:1.1.0"
but this is invalid for Espresso Tests, because fragment-testing includes an EmptyFragmentActivity class that is used to bootstrap the FragmentScenario. That Activity must exist in the runtime application's Manifest, and it cannot be in the androidTest manifest because those activities can only start in the instrumentation process, not the application's process. Therefore the documentation <
debugImplementation "androidx.fragment:fragment-testing:1.1.0"
There is an open issue to improve the documentation to clarify why it needs to be debugImplementation and not androidTestImplementation, and to call it out as an explicit requirement (so it cannot be perceived to be an oversight). That issue is:
But to better catch this common error, it would great to have a Lint check that will fail if a project tries to include the fragment-testing artifact in the androidTest configuration, when it should instead be debugImplementation.