IssueTracker

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.

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

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'

Yes, API 33 introduced this behavior, (internal) platform bug is here: b/247013643

I was incorrect, this is also reproducible on API 32 as well. Not reproducible on API 31.

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'.

I'm having issues on pre-33 api levels on a pure compose app (has all configChanges added in the manifest file) pared with AppCompatActivity just for multi language support. When changing the language I'm using AppCompatDelegate.setApplicationLocales(compat) which calls onConfigurationChanged on the activity. LocalConfiguration changes to the new configuration on 33+ but remains the same on pre-33. Workaround that i've found is calling if (Build.VERSION.SDK_INT < 33) contentView.dispatchConfigurationChanged(newConfig) in onConfigurationChanged. I'm guessing it's a compose issue since activity wise everything works as expected.

Thanks for the heads up, I've tried to find a related issue but only managed to find this one after a brief search.

Ok

Thanks for the heads up, I've tried to find a related issue but only managed to find this one after a brief search.

In a week, if no major issue is reported.

This should be available from Bumblebee too now.

Great, thank you 😊