[MaterialContainerTransform] Huge delay running transition on 1.3.0-alpha01

Description: 1.3.0-alpha01 causes MaterialContainerTransform to take way longer to run, and skip way more frames

Tried to update from 1.2.0-alpha06 but perf is a disaster.

Source code: Here’s how I’m launching the transition:

  private fun startContainerTransform(from: View, to: View): Flow<Boolean> {
    val channel = Channel<Boolean>()
    val transform = MaterialContainerTransform().apply {
      startView = from
      endView = to
      setPathMotion(MaterialArcMotion())
      scrimColor = Color.TRANSPARENT
      duration = 300L
      addListener(object : Transition.TransitionListener {
        override fun onTransitionEnd(transition: Transition) {
          channel.offer(true)
          channel.close()
        }

        override fun onTransitionResume(transition: Transition) {
        }

        override fun onTransitionPause(transition: Transition) {
        }

        override fun onTransitionCancel(transition: Transition) {
          Timber.e("Transition cancelled?")
          channel.offer(false)
          channel.close()
        }

        override fun onTransitionStart(transition: Transition) {
        }
      })
    }
    TransitionManager.beginDelayedTransition(screenContainer, transform)
    return channel.receiveAsFlow()
  }

This shows up in logcat:

Skipped 249 frames!  The application may be doing too much work on its main thread.

Android API version: 29

Material Library version: 1.3.0-alpha01

Device: Emulator Pixel 3a on API 29

[edenman]

fwiw I was seeing a bunch of bugs on the previous version too, sometimes the new view wouldn’t fully show, leading to the old view still being partially visible. Not sure if that’s relevant. Anyway I’m punting on container transform entirely and going back to good-old slide left/right for now.

[AxelBlaz3]

@dsn5ft I couldn’t reproduce the issue properly. I mean, there’s no jank in the sample app. Maybe because the data is static and not from server? My personal project app really lags for first few times and then everything will be fluid. What could be the possible reason behind that?

Personal app uses the MVVM architecture with Repository pattern. Also, dagger 2 is used for DI. Views are similar to the sample app. But still, the sample app is fluid. However, I face lag in personal app only for first few times of navigation from Home -> Detail screen and then everything will be fluid.