This is from https://github.com/google/accompanist/issues/1487:

I haven't been able to reproduce it without a lot of experimental APIs along with Navigation. But essentially given the following:

setContent {
val transition = updateTransition(...)
  transition.AnimatedContent {
    MyComposable()
  }
  if (transition.currentState == transition.targetState) {
    // area #3
  }
}

class MyComposable() {
  // area #1
  Scaffold(
    content = {
      // area #2
    }
  )
}

There are cases where the areas end up being composed in this order: 1, 3, 2 with AnimatedContent completing the transition and then the Scaffold composing its content.

The expectation was that it would always be 1, 2, 3 with the composition of the Scaffold content completing before the callback to area 3.

Is the expectation correct? Or does AnimatedContent completion have some priority over the Scaffold?

This could also be something going on in Scaffold, just wondering what the expectations are here.