-
Notifications
You must be signed in to change notification settings - Fork 1.9k
OS system components ignore app theme #22058
Copy link
Copy link
Closed
Labels
area-xamlXAML, CSS, Triggers, BehaviorsXAML, CSS, Triggers, Behaviorsplatform/windowss/triagedIssue has been reviewedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering TriageVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't workingSomething isn't working
Milestone
Metadata
Metadata
Assignees
Labels
area-xamlXAML, CSS, Triggers, BehaviorsXAML, CSS, Triggers, Behaviorsplatform/windowss/triagedIssue has been reviewedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering TriageVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for issues without a type.
Description
In the maui app, when the operating system theme is set opposite to that of the app itself, certain components such as the datepicker, keyboard, and navigation list animations display in the wrong theme.
This results in the components adopting the theme of the operating system, causing the user to see a component in the opposite color.
For example:
The app is set to the "Light" theme, but the user has their phone's theme set to "Dark." The app appears to the user in white, but native iOS/Android components like the datepicker and keyboard appear in the theme of the operating system, in this case, dark.
I've reproduced this on the following devices: Windows, Android, IOS
Please refer to the attached images for clarification.:


Steps to Reproduce
UserAppTheme = AppTheme.Dark;Link to public reproduction project repository
https://github.com/NiekRossenInfoSupport/maui-app
Version with bug
8.0.7 SR2
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
iOS, Android, Windows
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
No response