Error when moving Compose Desktop app between screens about decompose

[arkivanov]

Thanks for the report. However it's not clear what is the cause. Would it be possible to provide some code of the composables and components mentioned in the stack trace. Also the second exception seems like an internal Compose error, which might be the cause.

[ScottPierce]

You are right. Sorry, I'm doing too many things today - I opened up an issue with Compose here - JetBrains/compose-multiplatform#1687

[arkivanov]

From what I can understand from the stack trace, RootDeviceComponentImpl creates a Router in the init section, which in turn registers to the StateKeeper for stack preservation purposes. The latter has a check which verifies that there are no duplicate keys registered. This should not normally happen (unless there is a bug of course).
But then weird things happen. As far as I see, RootDeviceComponentImpl is being created from the RootComponentImpl.resolveChild method, which is called from RootComposableKt composable function.
It seems the RootDeviceComponentImpl gets duplicated somehow. Maybe because of the crash in Compose. To say something more accurate I would need some code of the mentioned components and composables.

[arkivanov]

Also worth to see how the very root component is initialised. A common mistake is to instantiate the root component inside a composable function without remember. Ideally it should be instantiated in the main function, before Compose is even started.

[ScottPierce]

I wasn't remembering the Components created. This is what caused the issue.