[BUG] java.lang.NoSuchMethodError: No direct method <init>(Ljava/lang/Object;Ljava/lang/Object;)V in class Landroidx/compose/animation/core/SeekableTransitionState;

[FunkyMuse]

Describe the bug When going back from a destination (scene) the app crashes with

To Reproduce Use Compose multiplatform 1.7.X-alpha or dev navigate from a destination, go back crash, not always

Expected behavior User should be returned to the destination safely

Minimal reproducible example I guess that's something introduced in 1.7.X Compose multiplatform that breaks the library

stack trace is

java.lang.NoSuchMethodError: No direct method <init>(Ljava/lang/Object;Ljava/lang/Object;)V in class Landroidx/compose/animation/core/SeekableTransitionState; or its super classes (declaration of 'androidx.compose.animation.core.SeekableTransitionState' appears in /data/app/~~49ENzoh7ld7afOHMt_9WzA==/com.x.x.debug-AIZoxjVS9E177qpLp0l5xQ==/base.apk)
                                                                                                        at moe.tlaster.precompose.navigation.NavHostKt$NavHost$6.invoke(NavHost.kt:191)
                                                                                                        at moe.tlaster.precompose.navigation.NavHostKt$NavHost$6.invoke(NavHost.kt:140)

[Tlaster]

Yes compose 1.7.x change the SeekableTransitionState's API, which I will update to use the new version after 1.7.x has been released.

[FunkyMuse]

Yes compose 1.7.x change the SeekableTransitionState's API, which I will update to use the new version after 1.7.x has been released.

1.7.X is in alpha now, maybe a PreCompose alpha/beta release too?