Skip to content

Fix time display format by using localized format - #101017

Merged
blimpich merged 5 commits into
Expensify:mainfrom
shubham1206agra:fix-date-locale
Sep 17, 2026
Merged

blimpich merged 5 commits into
Expensify:mainfrom
shubham1206agra:fix-date-locale

Conversation

@shubham1206agra

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #98088

Tests

  1. Open App
  2. On any report, verify that the time format written on top of the message is correct.
  3. On any trip detail, verify that the time format is correct.
  4. Verify that the time format is correct on status clear after.

PS - The time format is as follows:

Locale 00:05 08:00 12:00 14:05 23:10 Clock
en (en-US) 12:05 AM 8:00 AM 12:00 PM 2:05 PM 11:10 PM 12-hour
es 00:05 08:00 12:00 14:05 23:10 24-hour
fr 00:05 08:00 12:00 14:05 23:10 24-hour
de 00:05 08:00 12:00 14:05 23:10 24-hour
el 12:05 π.μ. 8:00 π.μ. 12:00 μ.μ. 2:05 μ.μ. 11:10 μ.μ. 12-hour
it 00:05 08:00 12:00 14:05 23:10 24-hour
ja 0:05 8:00 12:00 14:05 23:10 24-hour, unpadded
nl 00:05 08:00 12:00 14:05 23:10 24-hour
pl 00:05 08:00 12:00 14:05 23:10 24-hour
pt-BR 00:05 08:00 12:00 14:05 23:10 24-hour
zh-hans 上午 12:05 上午 8:00 下午 12:00 下午 2:05 下午 11:10 12-hour, marker first
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests

QA Steps

Same as Tests

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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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

Screen.Recording.2026-09-11.at.10.27.06.PM.mov

@shubham1206agra
shubham1206agra requested review from a team as code owners September 12, 2026 06:41
@melvin-bot
melvin-bot Bot requested review from dylanexpensify and linhvovan29546 and removed request for a team and linhvovan29546 September 12, 2026 06:41
@melvin-bot

melvin-bot Bot commented Sep 12, 2026

Copy link
Copy Markdown

@linhvovan29546 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]

@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: 01338eeb71

ℹ️ 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/pages/settings/Profile/CustomStatus/StatusClearAfterPage.tsx Outdated
@shubham1206agra

Copy link
Copy Markdown
Contributor Author

@roryabraham Switching from en-GB to en-US for timezone data for en locale has some tz rendering changes.

Timezone cases Before After
Case 1 (US Timezone) Screenshot 2026-09-12 at 12 17 42 PM Screenshot 2026-09-12 at 12 18 32 PM
Case 2 (EU Timezone) Screenshot 2026-09-12 at 12 19 24 PM Screenshot 2026-09-12 at 12 19 58 PM

@shubham1206agra

Copy link
Copy Markdown
Contributor Author

@blimpich Tagging you here as you wrote the issue #99345 and this PR is making the time display more robust to locale.

@codecov

codecov Bot commented Sep 14, 2026

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/index.ts 91.52% <ø> (ø)
src/components/LocaleContextProvider.tsx 85.48% <100.00%> (-0.24%) ⬇️
src/components/OnboardingHelpDropdownButton.tsx 95.65% <100.00%> (ø)
...ponents/ReportActionItem/ChronosOOOListActions.tsx 43.75% <ø> (ø)
src/pages/ScheduleCall/ScheduleCallPage.tsx 0.00% <ø> (ø)
src/pages/Travel/FlightTripDetails.tsx 100.00% <100.00%> (ø)
src/pages/Travel/HotelTripDetails.tsx 96.66% <100.00%> (ø)
...ages/ScheduleCall/ScheduleCallConfirmationPage.tsx 0.00% <0.00%> (ø)
src/pages/inbox/report/ParticipantLocalTime.tsx 92.00% <80.00%> (ø)
src/components/AutoUpdateTime.tsx 0.00% <0.00%> (ø)
... and 7 more
... and 450 files with indirect coverage changes

dylanexpensify
dylanexpensify previously approved these changes Sep 15, 2026

@dylanexpensify dylanexpensify 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.

Looks good from a product perspective 👍

@roryabraham

Copy link
Copy Markdown
Contributor

Switching from en-GB to en-US for timezone data for en locale has some tz rendering changes

These changes LGTM 👍🏼

@roryabraham

Copy link
Copy Markdown
Contributor

@linhvovan29546 looks like you were tagged above but unassigned due to some race condition. Please do C+ review here

@roryabraham
roryabraham self-requested a review September 16, 2026 03:54

@roryabraham roryabraham 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.

Mostly LGTM, one question 👍🏼

Comment thread src/libs/DateUtils.ts
return '';
}
return formatTimeWithPeriod(translate, new Date(dateTimeString), CONST.DATE.TIME_FORMAT_WITHOUT_PERIOD);
// Pinned to English, not the active language. This value is the TimePicker's wire format: it is parsed back by

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.

I'm a bit confused by this comment still - why not update both sides to locale-specific date format? Is it not display to the user?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@roryabraham This is mainly used to handle values which will be passed to BE, so we keep everything in English here.

roryabraham
roryabraham previously approved these changes Sep 16, 2026
@linhvovan29546

linhvovan29546 commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • 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 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Screen.Recording.2026-09-16.at.18.21.05.mov
Android: mWeb Chrome
Screen.Recording.2026-09-16.at.18.23.13.mov
iOS: HybridApp
Screen.Recording.2026-09-16.at.18.24.57.mov
iOS: mWeb Safari
Screen.Recording.2026-09-16.at.18.18.01.mov
MacOS: Chrome / Safari

Before
Screenshot 2026-09-16 at 17 13 00

After
Screenshot 2026-09-16 at 17 12 55

Screenshot 2026-09-16 at 17 17 14 Screenshot 2026-09-16 at 17 48 34 Screenshot 2026-09-16 at 18 34 42

@linhvovan29546

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: 87c97796c8

ℹ️ 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/CONST/index.ts
Comment thread tests/unit/DateUtilsTest.ts
@linhvovan29546

Copy link
Copy Markdown
Contributor

@shubham1206agra Spell check failed

@melvin-bot
melvin-bot Bot requested a review from roryabraham September 17, 2026 07:01
@blimpich
blimpich merged commit b22b075 into Expensify:main Sep 17, 2026
35 of 37 checks passed
@OSBotify

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.

@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

Copy link
Copy Markdown
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #101017.

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-b22b075-9e87e9f-953626c178eba1c2943915099254840e9931b597/index.html ❌ FAILED ❌
Android The QR code can't be generated, because the iOS build failed
Web 🕸️
https://101017.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/blimpich in version: 9.4.82-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

Help site changes are required

This PR changes user-visible behavior for a setting the help site already documents, so one article needed updating.

Draft PR: Docs updates for E/A#101017 time format follows Language setting

Why a docs change is needed

Switching CONST.DATE.LOCAL_TIME_FORMAT from the hardcoded h:mm a to date-fns' localized p token means the Language setting now decides whether times render on a 12-hour or a 24-hour clock (src/CONST/index.ts:695-699). Ten of the eleven shipped languages move to a 24-hour clock.

Account Settings documents the Language setting but never mentioned it affects the time format. A member switching to Español now sees 22:25 where they previously saw 10:25 PM, with nothing on the help site explaining why — a predictable "why did my times change" support question.

I confirmed the behavior in the running app on web rather than inferring it from the diff:

Verified Result
Chat timestamp with English selected Today at 10:25 PM — 12-hour clock
Chat timestamp after switching to Español Hoy a las 22:25 — 24-hour clock
Language settings labels Row and page title are both Language, under Account > Preferences

What the docs PR changes

Only docs/articles/new-expensify/settings/Account-Settings.md:

  • New ## What time format each language uses section with a per-language table of the clock convention and an example time for all 11 supported languages, plus where in the product times appear.
  • Two new FAQ entries: whether the time format can be set independently of the language, and why times switch to a 24-hour clock.
  • time format, 12-hour clock, and 24-hour clock added to the article keywords.

The clock convention per language comes from the table in your PR description. All UI labels and the language option names were checked against the live UI for exact capitalization. The article follows HELP_AUTHORING_GUIDELINES.md (single # title plus # FAQ, task-based ## headings only) and HELPSITE_NAMING_CONVENTIONS.md (bolded, UI-exact labels).

Articles I checked and ruled out
  • No other article in docs/articles documents the New Expensify time display format, so nothing else became stale.
  • Customize and Enforce Report Titles lists date format options, but those are report-title formulas and are unaffected by this change.
  • The English-language docs are unchanged in substance: English used a 12-hour clock before this PR and still does, so the en-GBen-US date-fns locale switch does not invalidate any English example.
  • The existing FAQ answer "Will changing my language affect reports?" remains accurate — it is about report content, not timestamp rendering — so I left it alone and added the time-format questions alongside it.

Checks run: npm run spell-changed (cspell, 0 issues) and ./.github/scripts/createDocsRoutes.sh (routes up to date). App has no prettier config or script, so that gate does not apply. No product code was touched, so the JS/TS gates are not in scope.


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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/blimpich in version: 9.4.86-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/blimpich in version: 9.4.89-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.4.89-0 🚀

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

Bundle Size Analysis (Sentry):

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.

7 participants