Filip Wiesner

04/12/2022, 2:33 PM
Hello, I've been struggling with accompanist
a lot lately. I've even filed a bug three weeks ago with no response. Does anyone have a workaround for this issue? It seems to me like a huge issue and I didn't see anyone talking about it which seems like it might be only on my end. Also, is the "official" support for navigation transitions coming anytime soon? The mandatory fade transitions were introduced back in January.

Ian Lake

04/12/2022, 2:39 PM
None of the transition APIs used by AnimatedNavHost (namely
) are stable APIs, so they still can't be used by Navigation itself, as explained in the original blog post:
They're still experimental because they are likely to change in significant, non-compatible ways with the introduction of shared elements
(of which we're also going to be building out support for in AnimatedNavHost)
It looks like that issue is assigned to the right person to take a look at it, but they've been working on Another earlier issue
I suspect you actually want to be using
and not
though 🙂

Filip Wiesner

04/12/2022, 3:45 PM
Sorry, I didn't want to sound like everything is supposed to work flawlessly. I know it is experimental and I know I am using alpha versions of both Compose and Accompanist. It just seems to me like it is a big issue. Btw it still happens with
. And I yeah, I forgot that shared element transitions are still in the works and a lot of stuff will be moving with it. Thanks for the explanation Ian 👍
I can see now that there are still issues from September of last year that are not resolved so three weeks is nothing 😄