Tash
02/05/2021, 9:38 PMViewModel
to cache state across configuration changes?Adam Powell
02/05/2021, 9:43 PMViewModel
entirely and just declare all config changes as handled for that activity in your manifest. Compose can handle those configuration changes without the activity restart at allTash
02/05/2021, 9:46 PMViewModel
. Will be interesting to get rid of that. Thank you!savedInstanceState
, so that takes care of that. Nice.Jordi Saumell
02/06/2021, 10:34 AMMark Murphy
02/07/2021, 5:06 PMjust declare all config changes as handled for that activity in your manifestI'm a bit nervous about this advice.
android:configChanges
would need to be reviewed with each Android release, as new configuration change types show up from time to time. IOW, there is no way to create a future-proof android:configChanges
value. Is there some trick to this that I missed along the way?
Also, is there anything in CTS that prevents a device manufacturer from adding some new sort of configuration change? Particularly an undocumented one?Adam Powell
02/07/2021, 6:05 PMviewModelScope
, which imo is a pretty bad idea whether you're working with compose or notJordi Saumell
02/07/2021, 10:54 PMAdam Powell
02/08/2021, 12:32 AMJordi Saumell
02/08/2021, 10:02 PM