Fixed
Status Update
Comments
il...@google.com <il...@google.com> #2
In Backward Compatibility (pre Android 13), the configuration is modified at the AppComaptActivity's level and hence the application context not getting modified is intended behaviour. Similar behaviour can be seen for nightMode.
ap...@google.com <ap...@google.com> #3
Hope this solves the question, please re-open if more information is required.
ap...@google.com <ap...@google.com> #4
Why is this the intended behavior? Appcompatdelegate that works halfways?
Can someone clarify?
Can someone clarify?
il...@google.com <il...@google.com> #5
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.
Description
AndroidX has increased the global
minSdk
to 19, which means the Fragment library can useandroid.os.CancellationSignal
instead ofandroidx.core.os.CancellationSignal
.This might be difficult, though, because there is an internal API surface shared between Fragment and Transition library that uses the compat class.