<State and Jetpack Compose> says "While remember h...

# compose

[Rick Regan]

State and Jetpack Compose says "While remember helps you retain state across recompositions, the state is not retained across configuration changes. For this, you must use rememberSaveable." On this channel, we've said that setting `android:configChanges`(as listed here) to handle the configuration changes would allow us to use plain old remember. Is it better to do the former or the latter?

[Colton Idle]

Even if you override all config changes you can still be restarted. See @Mark Murphy post on dynamic wallpapers.

[Rick Regan]

(I didn't state it in my question but I am talking about when you don't need the `remember`ed thing to also survive process death.)

[Andrey Kulikov]

if you don’t need the data to survive process death then your idea of remember+config changes would work fine

[Rob]

I found a bug that breaks onClick callbacks when density changes are handled by the activity. https://issuetracker.google.com/issues/223626955