"Configurations must be unique" error occurring in production

[pavel163]

I have a root component on our screen which includes four configurations: A, B, C, where each configuration corresponds to a different screen. According to the logic, configurations B and C can only be added to the stack with A. However, I encounter production cases where the stack forms as A, B, C, B, which contradicts the designed behavior, as navigating to any screen should first require returning to a state where only A is in the stack.

Multiple root components are showing this issue

[arkivanov]

Sorry but I don't understand the issue. Can you ask a question or describe in more details?

[pavel163]

I have a component similar to DefaultRootComponent, and it's organized in such a way that from one screen you can move to others (in the example these are Tabs). Over the last 90 days, there have been errors when a user navigated the following path: A (Tabs) -> B (DynamicFeatures) -> A (Tabs) -> C (CustomNavigation) -> A (Tabs) -> B (DynamicFeatures). For some reason, when these users returned to A (Tabs), the backstack was not cleared (the pop method was used for returning), and I receive the error java.lang.IllegalStateException - Configurations must be unique: [A, B, C, B].

[arkivanov]

It's hard to tell without any code or reproducer. Make sure you are using appropriate navigation functions. Duplicated configurations are not allowed. A possible issue is when the user double-clicks on a button or similar. Consider using pushNew for navigation.