IssueTracker

Are there many use cases for this? The current logic works fine with dark mode of platform, appcompat, and Compose.

When I was trying out integrating this with Now in Android, I ran into this issue since Now in Android currently doesn't inherit from AppCompatActivity and doesn't call AppCompatDelegate.setDefaultNightMode, so maybe the solution is instead to inherit from AppCompatActivity instead of just ComponentActivity to update the underlying configuration.

I just tested it with ComponentActivity. It's working fine for me. The scrim for 3-button nav and the icons are properly changed on light/dark mode switch. The extension function detect light/dark mode from resources.configuration.uiMode which is commonly used by the platform, AppCompat, and Compose, so I don't know why it doesn't work. Can I take a look at what you tried in Now in Android.

https://github.com/android/nowinandroid/tree/av/enable-edge-to-edge is the rough progress I made so far.

The theme switcher based on the user's preference within the app is handled separately from Configuration.uiMode and isn't updating the configuration directly, so I was attempting to call enableEdgeToEdge and manually specifying the dark and light themes.

The two options I see:

• Allow a different way of specifying for enableEdgeToEdge whether the app is effectively in dark mode or light mode instead of that being based just on Configuration.uiMode (this issue)
• Switch Now in Android to use AppCompatActivity and AppCompatDelegate.setDefaultNightMode so that the Configuration.uiMode is updated based on the user's preference

I see, so it has in-app light/dark setting.

On API 31+, apps with custom in-app light/dark settings should call UiModeManager.setApplicationNightMode to declare its theme to the system. This way, the system can use suitable colors duiring the splash screen. This should fix enableEdgeToEdge as well.

On API <31, it's easy if you can use AppCompatDelegate.setDefaultNightMode(int), but I can understand that you don't want to add appcompat dependency just for this.

So, custom mode is useful for apps that:

• Provide in-app light/dark mode settings on API <31.
• Don't want to depend on appcompat

I'm not sure if it's super common, but I guess the feature is worth implementing. I'll put it during the next alpha phase.

For Now in Android, I recommend you still call setApplicationNightMode on API 31+ regardless of enableEdgeToEdge. On API <31, just for the time being, you can either use the current e2e implementation, hide the setting, depend on appcompat, or just bear with the minor UI glitch. None of these are great, but I don't have a good solution now.

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.activity:activity:1.8.0-alpha06