cwa-app-ios
cwa-app-ios copied to clipboard
Colors in dark mode do not match
Avoid duplicates
- [x] Bug is not mentioned in the FAQ
- [?] Bug is specific for iOS only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
- [x] Bug is not already reported in another issue
Technical details
- Device name:
- iOS version:
- App version:
Describe the bug
Steps to reproduce the issue
- Activate darkmode
- Go to the your consent screen
Expected behaviour
Matching colors
Possible Fix
Match the color
Internal Tracking-ID: EXPOSUREAPP-7267
This affects more screens, like this one too:
It's hard to see but the section "Ermittlungszeitraum" has a different color than the elements above.
@jucktnich @Ein-Tim
Thank you both for the screenshots. I've forwarded the problem to the developers (EXPOSUREAPP-7267). Feel free to report other places where this happens iin this issue.
Corona-Warn-App Open Source Team
In this case, the color of the illustration does not match the background color.
@Ein-Tim will include this into internal ticket! Thanks!
@jucktnich
The case you mention in the OP has been fixed, https://github.com/corona-warn-app/cwa-app-ios/issues/2690#issuecomment-841478685 will be fixed in one of the next releases.
Only https://github.com/corona-warn-app/cwa-app-ios/issues/2690#issuecomment-839812566 isn't fixed yet.
@heinezen / @dsarkar Could you maybe update the internal ticket so that only https://github.com/corona-warn-app/cwa-app-ios/issues/2690#issuecomment-839812566 has to be fixed now.
@Ein-Tim Thanks, forwarded.
Please apply the "Fix 2.28" label to this issue, as it was fixed with https://github.com/corona-warn-app/cwa-app-ios/pull/4831.
@dsarkar Could you please ask the team if this is the intended look for that screen (background color of headline "Risiko-Ermittlung" differs from the rest of the background):
@dsarkar All issues in this thread have been fixed. It can be closed now.
Thanks for the information @Ein-Tim. As all issues in this thread have been fixed, I will now close this issue.