Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Although they sound similar, they serve different purposes. You are correct in thinking that putting uiMode into your android:configChanges allows your app to handle light/dark mode changes. It al...
Answer
#1: Initial revision
by
zmzaps
·
2024-06-29T05:40:15Z (5 months ago)
Although they sound similar, they serve different purposes. You are correct in thinking that putting `uiMode` into your `android:configChanges` allows your app to handle light/dark mode changes. It also handles more than that, see the links below. However, the `android:colorMode` attribute is not related to light/dark mode, and is instead related to color depth. Additionally, `colorMode` is not a valid value for `android:configChanges`. See: [https://developer.android.com/guide/topics/manifest/activity-element](https://developer.android.com/guide/topics/manifest/activity-element) Also see: [https://developer.android.com/reference/android/app/UiModeManager](https://developer.android.com/reference/android/app/UiModeManager)