Tash02/05/2021, 9:38 PM
to cache state across configuration changes?
Adam Powell02/05/2021, 9:43 PM
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 all
Tash02/05/2021, 9:46 PM
. Will be interesting to get rid of that. Thank you!
, so that takes care of that. Nice.
Jordi Saumell02/06/2021, 10:34 AM
Mark Murphy02/07/2021, 5:06 PM
just declare all config changes as handled for that activity in your manifestI'm a bit nervous about this advice.
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
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 Powell02/07/2021, 6:05 PM
, which imo is a pretty bad idea whether you're working with compose or not
Jordi Saumell02/07/2021, 10:54 PM
Adam Powell02/08/2021, 12:32 AM
Jordi Saumell02/08/2021, 10:02 PM