Status Update
No update yet.
Comments
il...@google.com
Attached reproducing video of an app using calculateWindowSizeClass and LocalConfiguration:
On the second time resizing to be 50%/50% from smaller, the displayed configuration is incorrect.
il...@google.com
When resizing the activity in multi-window mode under those conditions, there are cases where:
the Activity is not recreated Activity.onConfigurationChanged is not called View.onConfigurationChanged is not called
Is this just for 33 / is there a framework bug filed? The amount of broken things in configuration land we already had to workaround in Compose is a bit untenable. It seems like we are missing a lot of test coverage in the platform to avoid these issues hitting us in the future
il...@google.com
In any case this seems like more ammunition for us to push more strongly on 'pure-compose apps should always opt out of configuration changes'
il...@google.com
ap...@google.com
Yes, API 33 introduced this behavior, (internal) platform bug is here:
ap...@google.com
I was incorrect, this is also reproducible on API 32 as well. Not reproducible on API 31.
ap...@google.com
Adam/Louis, how do we want to handle this one? Is there someone on platform who should take this, or since API 32 is already out in the wild maybe this should go to devrel to push more strongly on 'pure-compose apps should always opt out of configuration changes'.
Description
Version used: 1.4.0-alpha01
Devices/Android versions reproduced on: Android S
It's currently not possible to build an app which depends on fragment-testing for Android S since it depends on androidx.test:core:1.3.0 which does not properly export activities with intent filters.
androidx.test:core:1.4.0 fixes this.