Fix localization: dates not being localized correctly

[sofi-a]

Explanation of Change

Reverts

• [CP Staging] Revert "Fix localization: dates not being localized correctly" #76684

Fixes

• Android - Expense-App crashes on opening split expense #76643
• Profile - Selected date in the calendar is moved back by one day #76646

Fixed Issues

$ #69562
PROPOSAL: #69562 (comment)

Tests

Calendar/Date Picker

1. Navigate to Account > Preferences.
2. Set **Language preference = English.
3. Navigate to Account > Profile.
4. Click Status.
5. Under Clear after, select Custom.
6. Open the Date picker.
7. Verify that:
   • The start of the week is “S” (Sunday).
   • Month names are displayed in English (e.g., “January”).
8. Navigate back to Account > Preferences.
9. Set Language preference = Español.
10. Return to the Status > Clear after > Custom > Date picker.
11. Verify that:
    • The start of the week is “L” (lunes).
    • Month names are displayed in Spanish (e.g., “Enero”).

Note

In Firefox the start of the week is always Monday, regardless of language setting, due to browser limitations.

Before	After

Chat

1. Navigate to Account > Preferences.
2. Set Language preference = English.
3. Navigate to any chat or thread.
4. Verify that the date and time are displayed using English formatting:
   • Chat participant’s local time: "It’s 11:52 PM for John" or "It’s 11:52 PM Saturday for John".
   • Sent time and thread indicator: "Sep 7, 2025 at 7:35 PM" or "Yesterday at 5:32 AM".
   • Expense preview: "Sep 6" or "Oct 17, 2023".
5. Navigate back to Account > Preferences.
6. Set Language preference = Español.
7. Return to the chat or thread.
8. Verify that date and time are displayed using Spanish formatting:
   • Chat participant’s local time: "Son las 23:51 para John" or "Son las 11:51 sábado para John".
   • Sent time and thread indicator: "20 nov 2023 a 15:03" or "Hoy a las 10:20".
   • Expense preview: "sep 3" or "18 may 2023".

Before	After

Profile Page

1. Navigate to Account > Preferences.
2. Set Language preference = English.
3. Navigate to any chat or thread.
4. Click on a user’s avatar.
5. On the profile page, verify that the user’s local time is displayed using English formatting, e.g.: 12:58 AM GMT+3
6. Navigate back to Account > Preferences.
7. Set Language preference = Español.
8. Return to the chat or thread.
9. Click on a user’s avatar.
10. On the profile page, verify that the user’s local time is displayed using Spanish formatting, e.g.: 12:58 GMT+3

Before	After

Search Page

1. Navigate to Account > Preferences.
2. Set Language preference = English.
3. Navigate to Reports > Expenses.
4. Verify that the values under the Date column are displayed using English formatting, e.g.: "Sep 6" or "Sep 6, 2024"
5. Navigate back to Account > Preferences.
6. Set Language preference = Español.
7. Return to Reports > Expenses.
8. Verify that the values under the Date column are displayed using Spanish formatting, e.g.: "sep 6" or "28 oct 2023"

Before	After

Subscription Page

1. Navigate to Account > Preferences.
2. Set Language preference = English.
3. Navigate to Account > Subscription.
4. Verify that the following dates are displayed using English formatting:
   • Subtitle date
   • Next billing date
   • Card section date
5. Navigate back to Account > Preferences.
6. Set Language preference = Español.
7. Return to Account > Subscription.
8. Verify that the following dates are displayed using Spanish formatting:
   • Subtitle date
   • Next billing date
   • Card section date

Before	After

• Verify that no errors appear in the JS console

Offline tests

Since changing the language preference requires an internet connection, tests cannot be performed offline.

QA Steps

Same as tests

• 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
  • MacOS: Desktop
• 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

Android: Native

Screen.Recording.2025-10-02.at.1.10.16.in.the.afternoon.mov

Android: mWeb Chrome

Screen.Recording.2025-10-02.at.2.00.12.in.the.afternoon.mov

iOS: Native

Screen.Recording.2025-09-08.at.4.23.15.in.the.afternoon.mov

iOS: mWeb Safari

Screen.Recording.2025-09-08.at.4.25.20.in.the.afternoon.mov

MacOS: Chrome / Safari

Screen.Recording.2025-09-08.at.3.13.36.in.the.afternoon.mov

MacOS: Desktop

Screen.Recording.2025-09-08.at.4.34.57.in.the.afternoon.mov

[melvin-bot]

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
src/CONST/index.ts	83.89% <100.00%> (+0.13%)	⬆️
...s/DatePicker/CalendarPicker/generateMonthMatrix.ts	100.00% <100.00%> (ø)
src/components/DatePicker/CalendarPicker/index.tsx	84.04% <100.00%> (+0.17%)	⬆️
src/components/LHNOptionsList/OptionRowLHN.tsx	95.77% <100.00%> (+0.06%)	⬆️
.../components/MoneyRequestConfirmationListFooter.tsx	84.07% <100.00%> (ø)
...ponents/ReportActionItem/ChronosOOOListActions.tsx	0.00% <ø> (ø)
...m/TransactionPreview/TransactionPreviewContent.tsx	76.08% <ø> (ø)
...rc/components/ReportActionItem/TripDetailsView.tsx	32.78% <ø> (ø)
...rc/components/ReportActionItem/TripRoomPreview.tsx	0.00% <ø> (ø)
...ents/SelectionListWithSections/Search/DateCell.tsx	100.00% <100.00%> (ø)
... and 27 more
... and 10 files with indirect coverage changes

[melvin-bot]

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

[iwiznia]

@sofi-a conflicts.
@akinwale please review this or reassign to another C+ if you don't have the time

[akinwale]

I'll start reviewing today.

[akinwale]

@sofi-a bump on fixing merge conflicts.

[akinwale]

@sofi-a bump.

[akinwale]

@sofi-a Could you update the OP with all the test steps?

[akinwale]

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 there are no new alerts related to the canBeMissing param for useOnyx
• I verified proper code patterns were followed (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 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)
• 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
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • 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
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • 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 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 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.
• 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

78251-android-hybrid.mp4

Android: mWeb Chrome

78251-android-chrome.mp4

iOS: HybridApp

78251-ios-hybrid.mp4

iOS: mWeb Safari

78251-ios-safari.mp4

MacOS: Chrome / Safari

78251-web.mp4

[akinwale]

LGTM.

@sofi-a Please add the test steps in the thread OP so that we can get this merged.

[iwiznia]

Conflicts

[akinwale]

@sofi-a The TypeScript checks are failing. Could you check this?

[akinwale]

@iwiznia Ready to merge.

[OSBotify]

✋ 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]

🚀 Deployed to staging by https://github.com/iwiznia in version: 9.3.5-0 🚀

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

[youssef-lr]

This is causing a crash when merging. I'm fixing it here #80029

[OSBotify]

🚀 Deployed to production by https://github.com/Beamanator in version: 9.3.5-7 🚀

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