⁉️ I am having trouble with

ComposeTestRule#advanceTimeBy

method. It doesn’t work as expected with animations. ▶️ Here’s more details : https://stackoverflow.com/questions/70982285/compose-advancetimeby-doesnt-work-with-animation.

Some initial investigation showed that the animations from

AnimatedVisibility

were never added to the Transition, because measure() was not called and slide animation is initialized during measure. As a result, we ended up having an empty Transition that finished right away. That's why the test failed. Note that adding

advanceTimeByFrame()

before

advanceTimeBy(1500)

seems to allow the test to pass. This might be useful for narrowing down the cause. Could you file a bug please?

Workaround works! Confirmed. Sure. I’ll file a ticket 👍

Hey, I am fairly new to compose but for some reason, after updating to compose 1.1.1.

rule.onNodeWithText("title").assertDoesNotExist()
    rule.mainClock.autoAdvance = false

    rule.runOnUiThread { expanded = true }
    rule.mainClock.advanceTimeByFrame() // Trigger the popup
    rule.waitForIdle()
    rule.mainClock.advanceTimeByFrame() // Kick off the animation
    rule.mainClock.advanceTimeBy(InTransitionDuration.toLong())
    rule.onNodeWithText("title").assertExists()

the code assertExists() doesn't complete and the test hangs on that step. We run the test as instrumentation and unit test using Robolectric. The instrumentation test seems to get executed but facing problem with running as unit test. Any thoughts ? @Doris Liu @theapache64

Two questions: 1. Can you log the value of

InTransitionDuration

, to double check it's within reasonable range and isn't nano-second based. 2. Did this work before 1.1.1?

1. We have set the

InTransitionDuration

to 120, thats the same to the duration of the animation. 2. Yes, it worked with compose version 1.0.5 (currently used version). But as we were trying to migrate to 1.1.0 or 1.1.1, it fails on both version

In that case, this sounds like a bug to me. Could you file a bug, including the snippet?

sure. Is there anything specific related animation that got changed in the 1.1.0 version? Running the test as instrumentation seems to work fine but causing a problem while running it as unit test with robolectric

Here's all the changes in animation: https://developer.android.com/jetpack/androidx/releases/compose-animation Nothing stands out. It could also be a change in testing that caused the issue.

A little more context on this (I work with Rohil) - this is only happening in our Robolectric Junit tests, not instrumented tests. I suspect there’s something funky happening with Robolectric’s shadows.