IssueTracker

AppCompatDelegate generally works at the Activity level. This is the case with other features such as NightMode as well. This is why it is intended that it does not affect the application context.

I'm re-assigning this to the team to assess the feasibility of extending the feature to alter the application context.

We recently added a language picker to our alarm app with ~5M downloads. We were enthused when we heard of Android 13's per-app language capabilities and back-porting.

However, in practice this is a half-baked pre-Android 13 implementation. Anyone who implements it is going to have to handle attachBaseContext() in the Application.kt, Services, and any activity that doesn't extend AppCompatActivity.

If no changes are made, I would at least suggest adding to the Per-app language preferences documentation about the attachBaseContext() for pre-Android 13, and suggested implementation for it - please don't make 1000s of developers write this code :)

Thanks!

It is common use case, to be able to get string from application context besides activity & fragment. If pre-13 unable exhibit same behavior as 13 (able to get localized string from application context), then AppCompatDelegate.setApplicationLocales doesn't solve the backward compatible issue.

Due to this limitation, we can only provide such a dynamic language feature, for Android 13 only.

Hacked