Fixed
Status Update
Comments
sj...@google.com <sj...@google.com>
al...@google.com <al...@google.com>
ju...@google.com <ju...@google.com>
ar...@google.com <ar...@google.com>
ap...@google.com <ap...@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.
ar...@google.com <ar...@google.com>
lb...@gmail.com <lb...@gmail.com> #3
Hope this solves the question, please re-open if more information is required.
ar...@google.com <ar...@google.com> #4
Why is this the intended behavior? Appcompatdelegate that works halfways?
Can someone clarify?
Can someone clarify?
na...@google.com <na...@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.
lb...@gmail.com <lb...@gmail.com> #6
Hello, is there any update regarding to this behavior? Or any known workaround to avoid this issue? Thanks
Description
The purpose of NotificationManagerCompat is to be able to use it instead of the normal one, but it doesn't seem complete because this function is missing.