Skip to content

Add highcontrast btn in signin page and sync it with server values#92117

Merged
luacmartins merged 23 commits into
Expensify:mainfrom
rushatgabhane:home-high-contrast
Jun 5, 2026
Merged

Add highcontrast btn in signin page and sync it with server values#92117
luacmartins merged 23 commits into
Expensify:mainfrom
rushatgabhane:home-high-contrast

Conversation

@rushatgabhane

@rushatgabhane rushatgabhane commented May 29, 2026

Copy link
Copy Markdown
Member

Explanation of Change

Fixed Issues

$ #92049
PROPOSAL:

Tests

Tests: high contrast on sign-in

  1. On Sign in page, verify that "Enable high contrast" button shows above language selector.
  2. Tap the button
  3. Verify thatpage goes high-contrast.
  4. Tap again. Verify page is normal contrast.
  5. Sign in and verify that the theme updates to contrast version of whatever the past theme was.

Post login

  1. Set the server theme as System and enable high contrast
  2. Sign out. Verify that theme stays system-contrast
  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as QA

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2026-05-29.at.23.23.48.mov

@melvin-bot

melvin-bot Bot commented May 29, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

Comment thread src/libs/actions/User.ts Outdated
Comment thread src/libs/Navigation/AppNavigator/AuthScreensInitHandler.tsx Outdated
Comment thread src/libs/Navigation/AppNavigator/AuthScreensInitHandler.tsx Outdated
Comment thread src/libs/Navigation/AppNavigator/AuthScreensInitHandler.tsx Outdated
Co-authored-by: Rushat Gabhane <rushatgabhane@gmail.com>
@rushatgabhane rushatgabhane marked this pull request as ready for review May 29, 2026 21:42
@rushatgabhane rushatgabhane requested review from a team as code owners May 29, 2026 21:42
@melvin-bot melvin-bot Bot requested review from Eskalifer1 and JmillsExpensify and removed request for a team May 29, 2026 21:42
@melvin-bot

melvin-bot Bot commented May 29, 2026

Copy link
Copy Markdown

@Eskalifer1 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot Bot requested review from a team and Krishna2323 and removed request for a team May 29, 2026 21:42
@melvin-bot

melvin-bot Bot commented May 29, 2026

Copy link
Copy Markdown

@Krishna2323 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Comment thread src/libs/Navigation/AppNavigator/AuthScreensInitHandler.tsx Outdated
@rushatgabhane

rushatgabhane commented May 29, 2026

Copy link
Copy Markdown
Member Author

I need to increase width of language selector i guess

Screenshot 2026-05-29 at 23 49 29

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7f87a7e0d3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/libs/Navigation/AppNavigator/AuthScreensInitHandler.tsx Outdated
@codecov

codecov Bot commented May 29, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/CONST/index.ts 93.79% <ø> (ø)
src/ONYXKEYS.ts 100.00% <ø> (ø)
...rc/components/Icon/chunks/expensify-icons.chunk.ts 0.00% <ø> (ø)
...Navigation/AppNavigator/AuthScreensInitHandler.tsx 96.66% <100.00%> (+0.05%) ⬆️
src/libs/actions/App.ts 51.44% <ø> (ø)
src/pages/signin/Licenses.tsx 100.00% <100.00%> (ø)
src/pages/signin/SignInPage.tsx 75.18% <100.00%> (+0.36%) ⬆️
src/components/HighContrastModeSwitcher.tsx 87.50% <87.50%> (ø)
src/hooks/useReconcileHighContrastIntent.ts 71.42% <71.42%> (ø)
src/libs/actions/User.ts 36.26% <37.50%> (+0.02%) ⬆️
... and 11 files with indirect coverage changes

@rushatgabhane

Copy link
Copy Markdown
Member Author

Updated the width

Screenshot 2026-05-30 at 00 09 52

@rushatgabhane rushatgabhane requested a review from a team as a code owner May 29, 2026 22:10
@rushatgabhane

Copy link
Copy Markdown
Member Author

I still need svg for this icon

Image

@Eskalifer1

Copy link
Copy Markdown
Contributor

Actually i can reproduce probably the same bug on staging, so it's now related to our changes

2026-06-03.13.13.44.mov

@Eskalifer1

Copy link
Copy Markdown
Contributor

Let's merge main to fix eslint+ts

@Eskalifer1

Copy link
Copy Markdown
Contributor

What should we do about this bug? Should we just ignore it here, or is this actually the expected behavior and supposed to be that way?

If we don't fix this here, within the scope of this PR, then I haven't found any other issues

@rushatgabhane

rushatgabhane commented Jun 3, 2026

Copy link
Copy Markdown
Member Author

Hi @rushatgabhane, i can still reproduce #92117 (review)...

we do theme reconciliation when the user signs in - and not when they click sign in button (this is session only)

maybe there is an easy fix. but i don't think we should block on it

@rushatgabhane

Copy link
Copy Markdown
Member Author

@Eskalifer1 all yours! thank you for the extensive review

@Eskalifer1

Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 490dc31164

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/libs/actions/User.ts Outdated
@Eskalifer1

Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Swish!

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@Eskalifer1 Eskalifer1 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

I'm going to be OOO all next week. So wi will not be able to do smth with regressions if they appear...

@melvin-bot

melvin-bot Bot commented Jun 5, 2026

Copy link
Copy Markdown

We did not find an internal engineer to review this PR, trying to assign a random engineer to #92049 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

@melvin-bot melvin-bot Bot requested a review from luacmartins June 5, 2026 13:59

@luacmartins luacmartins left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@luacmartins luacmartins merged commit 0c5539a into Expensify:main Jun 5, 2026
35 checks passed
@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

🚧 @luacmartins has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

OSBotify commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

OSBotify commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.4.0-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 Reviewed this PR for help site impact under App/docs/articles.

Help site changes are required. This PR adds an Enable high contrast button to the logged-out sign-in screen (above the language selector), letting users turn on high contrast mode before signing in. The existing Account Settings article only documented enabling high contrast from Account > Preferences > Theme while signed in, so the new sign-in screen flow was undocumented.

I created a draft help site PR: #92805

  • Added a task-based section How to enable high contrast mode from the sign-in screen to docs/articles/new-expensify/settings/Account-Settings.md.
  • Used the exact UI labels verified against source (src/languages/en.ts, HighContrastModeSwitcher.tsx, Licenses.tsx): Enable high contrast / Disable high contrast, positioned above the language selector.

@rushatgabhane, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review

@mitarachim

Copy link
Copy Markdown

Deploy Blocker #92824 was identified to be related to this PR.

@OSBotify

OSBotify commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Julesssss in version: 9.4.0-7 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

const icons = useMemoizedLazyExpensifyIcons(['Moon']);

const currentTheme = preferredTheme ?? CONST.THEME.DEFAULT;
const isHighContrast = isHighContrastTheme(currentTheme);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The button state should be consistent with the UI, which takes the user's intended theme into account:

const isHighContrast = highContrastIntent ?? contrastThemes.includes(preferredTheme ?? '');

Fixed via #92978.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants