Closed yeldar-nurpeissov closed 4 months ago
The hashString
function also takes into account qualifiedName
of the configuration class. This is a bug introduced in the recent version 3.2.0-alpha01
with DecomposeExperimentFlags.duplicateConfigurationsEnabled
flag enabled. I will fix it, thanks!
Should be fixed in version 3.2.0-alpha02.
I have two components with config classes that have identical properties, like ID. Navigating from the first to the second component with the same hash-coded arguments causes an error:
java.lang.IllegalArgumentException: Key kotlin.Pair_173 was used multiple times.
For example:
If both song and singer have id = "1", navigating to the song screen works, but navigating to the singer screen results in the error.
The configs don't have to be in the same component to trigger this error.
IMHO,
hashString()
generates a hash from arguments.Children
ComposableHere is a sample code that produces the error.
Version: 3.2.0-alpha01