TestLifecycleOwner hangs inside of runTest [259344129]

Fixed

Bug

Status Update

No update yet.

Description

ji...@gmail.com

created issue #1

Nov 16, 2022 07:11PM

Component used: TestLifecycleOwner

Version used: 2.5.1

Devices/Android versions reproduced on: N/A

When used inside of runTest,

@OptIn(ExperimentalCoroutinesApi::class, ExperimentalStdlibApi::class)
class TestLifecycleOwnerTest {
  @Test
  fun testLifecycleOwnerStuff() = runTest(dispatchTimeoutMs = 5000) {
    Dispatchers.setMain(coroutineContext[CoroutineDispatcher]!!)
    val lifecycleOwner = TestLifecycleOwner()

    lifecycleOwner.currentState = Lifecycle.State.RESUMED
    Dispatchers.resetMain()
  }
}

...will hang and never return (not even after dispatchTimeoutMs expires)

Comments

sa...@google.com <sa...@google.com> #2Nov 16, 2022 09:28PM

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).

ji...@gmail.com <ji...@gmail.com> #3Nov 16, 2022 10:11PM

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> May 10, 2023 11:13PM

Assigned to sa...@google.com.

sa...@google.com <sa...@google.com> Aug 7, 2023 01:03PM

Accepted by sa...@google.com.

ap...@google.com <ap...@google.com> #4Aug 25, 2023 04:53PM

Marked as fixed.

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).

il...@google.com <il...@google.com> #5Aug 29, 2023 04:03PM

@ #4:

I think that is intended for Animator. If you set the currentPlayTime to 0 or the total duration the animator completes. We do some special checks in fragments to handle it.

pr...@google.com <pr...@google.com> #6Sep 6, 2023 07:56PM

Did some investigation on the Fragment side and it seems like the merged transition is targeting correctly.

Exiting Transition: Slide@aa9288e: tgts(android.widget.LinearLayout{f9add3d})
>>>>> ExitingViews <<<<<
View: android.widget.LinearLayout{f9add3d}
Entering Transition: Slide@35b8af: tgts(android.widget.LinearLayout{b7f24bc})
>>>>> EnteringViews <<<<<
View: android.widget.LinearLayout{b7f24bc}
Final merged transition: TransitionSet@7bc1c45: 
      TransitionSet@e133f9a: 
        Slide@aa9288e: tgts(android.widget.LinearLayout{f9add3d})
      Slide@35b8af: tgts(android.widget.LinearLayout{b7f24bc})
merged transition passed to controlDelayedTransition: TransitionSet@7bc1c45: 
      TransitionSet@e133f9a: 
        Slide@aa9288e: tgts(android.widget.LinearLayout{f9add3d})
      Slide@35b8af: tgts(android.widget.LinearLayout{b7f24bc})

Still digging.