-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Theme Switching] 🐛 Android - Scan - Capture error and camera access pop-ups are not in dark mode #33138
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
Triggered auto assignment to @jasperhuangg ( |
This seems to be the same issue as #33120 (the same component), and we're not blocking deploy on that one so I don't think we should block deploy here either. |
@grgia Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Closing this in favor of #33235 |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.13-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Precondition:
Expected Result:
The pop-ups in Step 3 and 4 are in light mode
Actual Result:
The capture error and camera access pop-ups in Step 3 and 4 respectively remain in dark mode
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6313917_1702605474626.Screen_Recording_20231215_093943_New_Expensify.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: