I do have a problem with compose-multiplatform and the newly added ExposedDropdownMenu. More in thre...

# compose

[Jan]

I do have a problem with compose-multiplatform and the newly added ExposedDropdownMenu. More in thread:

[Jan]

The ExposedDropDownMenu on Android does not display my initial selected element while on iOS its working, see picture (left android, right ios). Is that a known issue with compose-multiplatform 1.5.10-beta02

[Jan]

@Ivan Matkov maybe you know about it?

[Ivan Matkov]

JetBrains doesn't change Android anyhow. In Compose Multiplatform projects our plugin includes original Google's artifact to your Android app. So, it's better to ping Google folks about Android-only issues

[Jan]

ah, ok. thanks for bothering you

[Jan]

In my composable I do the follwing:

val uiState: InventoryComponentViewModel.UiState by component.uiState.collectAsState()
    var selectedVenue by remember { mutableStateOf(uiState.selectedVenue) }

[Jan]

within uiState I have a property selectedVenue. If I debug my code its set in uiState but its not set in my selectedVenue variable. While evaluating these two expressions its says the following:

[Jan]

Image from iOS.jpg

[Pablichjenkov]

What happens if you set uiState as the key for remember

[Jan]

let me check

[Jan]

this works, but If I change the value afterwards and rotate the device the initial (first) value is displayed again

[Jan]

nice!

[Jan]

the issue regarding rotation was my fault

[Jan]

can you explain why its working?

[Jan]

and strange that its working on ios ...

[Pablichjenkov]

It is due to positional memoization Leland Richardson has a good talk about that. Basically remember works by keeping the initial value from one composition to another composition. Without a key, remember uses its position in the slot table to determine if it was existing in the previous composition. And if it matches, it will pick the previous composition value, ignoring the value you pass in the composable function parameter.

[Pablichjenkov]

So it is advisable to use keys with remember and LaunchEffect. In the case of iOS, if you follow the iOS issues, there is currently an open issue where iOS triggers more than one composition at startup. Perhaps that is updating something somewhere, making it work. I would have to see more in detail to see what is going on.