Status Update
No update yet.
Comments
ys...@google.com
cc...@google.com
As Yuri links above, Macrobenchmark doesn't set this, AndroidX does.
You can change this for your module, though we haven't evaluated this broadly. Ideally we like it off for startup, but on for other interactions - thankfully it doesn't apply to scrolling, so we haven't tried to change the default.
After tests are finished, all animations ( in dev settings) got disabled .
That sounds like a platform bug, since this resolves down to the --no-window-animation flag passed to activity manager - it's the platform's responsibility to re-enable animations after the instrumentation is complete. Suggest filing an internal bug with repro for that. Happy to help you break it down to a couple of APKs + an am instrument command, which may help them reproduce without checking out AndroidX. Also +cc Chet who may have been the last one to touch it.
Description
Component used: Macrobenchmark Version used: TOT AndroidX Devices/Android versions reproduced on: API 33
Macrobenchmark tests running without animations on API 33. After tests are finished, all animations ( in dev settings) got disabled .
Steps to reproduce
That was reproduced on Wear 4 ( API 33) device.
Workaround: Animations can be enabled by setting the flag
testOptions.animationsDisabled = falsein android section in Gradle flag