A modern programming language that makes developers happier.

kotlinlang

I have a question about `AnimatedNavHost` from Accompanist. Is the default enter animation different based on the root element of the target composable ? Or I’m missing something ? Is this documented ?

Based on <https://github.com/google/accompanist/blob/main/navigation-animation/src/main/java/com/google/accompanist/navigation/animation/AnimatedNavHost.kt#L83-L86|https://github.com/google/accompanist/blob/main/navigation-animation/src/main/java[…]/com/google/accompanist/navigation/animation/AnimatedNavHost.kt>, it seems to be the same regardless of initial/target.

I noticed a different entry animation between composables that have a `Column` on top and those that have `Scaffolds`

I didn’t specify any animation in the navhost

Yeah, there's currently a bug when animating from a Scaffold screen to a non-Scaffold screen. There is <https://github.com/google/accompanist/issues/729>, but there should probably also be a bug report somewhere.

Or … at least I think it's a bug. It seems like something that generally _should_ work, but doesn't really right now.

I'd first make sure the size of your AnimatedNavHost isn't changing - i.e., it has a fixed size in whatever contains it. The animations default to being centered in the size so if the size changes, it is going to look different

You're absolutely right, my bad! I had “fixed” this for our app recently, and did so by wrapping stuff in a Scaffold. But I suppose that worked because Scaffold itself fills the screen size, then?

Thank you so much Ian, I will try to check the dimensions of the components. A few weeks ago I posted a question related to this, but I’ll close it or put a reference to your message.

<https://stackoverflow.com/questions/69380349/animatednavhost-default-enter-animation-is-different-if-the-target-has-no-scaffo>