Zach Klippenstein (he/him) [MOD]02/09/2021, 8:27 PM
noticed that the view state of their nested Android view hierarchies isn’t being restored correctly either after config changes or navigation, or weird stuff with lifecycles? I’ve been exploring some of these interactions and found what I’m pretty sure are a number of bugs. The README in this repo describes a number of the (potential) issues I found, but if people have found other repro cases it would probably be good to add them to the Google issue.
aiidziis02/09/2021, 8:29 PM
Halil Ozercan02/09/2021, 8:30 PM
Zach Klippenstein (he/him) [MOD]02/09/2021, 9:06 PM
Ian Lake02/10/2021, 1:40 AM
Zach Klippenstein (he/him) [MOD]02/10/2021, 2:40 AM
Ian Lake02/10/2021, 3:10 AM
Zach Klippenstein (he/him) [MOD]02/10/2021, 3:12 AM
aiidziis02/12/2021, 2:20 PM
Zach Klippenstein (he/him) [MOD]02/12/2021, 3:05 PM
julioromano02/12/2021, 11:20 PM
called but not
? (re: https://kotlinlang.slack.com/archives/CJLTWPH7S/p1613139840305500 )
Zach Klippenstein (he/him) [MOD]02/12/2021, 11:20 PM
julioromano02/12/2021, 11:30 PM
I can confirm this happens with alpha12 even when not using
Android onRestoreInstanceState for Android views nested in ComposeViews is very broken, even when all known views have their IDs set: It's not called after config changes.
: it is enough if the
composable is loaded inside an Activity’s
Zach Klippenstein (he/him) [MOD]02/12/2021, 11:59 PM
) – i should probably have been more precise about that in the readme, I just said
since that’s the primary API that you’re probably going to use if you do a lot of switching between worlds like this.