Is it possible that on compose version 1.1.1. The ...

# compose-android

[Pablichjenkov]

Is it possible that on compose version 1.1.1. The material Text {} skips text updates?

[Pablichjenkov]

I have a Composable that receives around 5 state updates sequentially one right after another. My logs show that the last update is not what the Text Composable painted. Snapshot state value updates are ok.

[Pablichjenkov]

TextField works ok

[Pablichjenkov]

Seems to take only one update.

[Csaba Szugyiczki]

I think it would help if you shared the minimum amount of code that is needed to reproduce this

[Pablichjenkov]

On my phone now, I will later. I workaround it by emitting a new Text{} based on state.

[Pablichjenkov]

Bellow are the state and composable files. The composable ConnectionInfo gets called multiple times very often.

ConnectionInfo.ktConnectionInfoState.kt

[Pablichjenkov]

Important to notice that this code is using compose compiler 1.1.1 and material 1.1.1. I will update to compose compiler 1.3.2 and material 1.3.1. Perhaps the update fixes it.

[Csaba Szugyiczki]

hmm, thats strange. If you log the value of the text variable, you can see it change in the logs just fine?

[Pablichjenkov]

Yes, I do that, I had a log right in the line above and can see every new title value. It is strange right.

[Csaba Szugyiczki]

Based on the code you posted I think it should work fine, I am really curious if the compiler update will solve the issue

[Pablichjenkov]

I believe so. I LL post the results