Fix CJK chart axis labels by using numeric-only formats

[MelvinBot]

Explanation of Change

The Skia canvas font (ExpensifyNeue-Regular) used in chart rendering lacks CJK (Chinese/Japanese/Korean) character glyphs. When the app language is set to Chinese or Japanese, date-fns produces localized month names containing CJK characters (e.g., "一月 2025" in Chinese, "1月 2025" in Japanese). Since Skia's text rendering uses only the loaded font with no fallback chain (unlike React Native's <Text> which uses platform font fallback), these characters render as broken/blank glyphs on chart axis labels.

This PR changes the chart getLabel functions for month, week, and quarter group-by types to produce Latin-character-only labels:

• Month: MM/YYYY (e.g., 01/2026) instead of locale-formatted month name
• Week: MM/DD/YYYY (e.g., 01/06/2026) instead of locale-formatted date range
• Quarter: Q{n} YYYY (e.g., Q1 2026) instead of format that includes locale month names

The locale-formatted strings (formattedMonth, formattedWeek, formattedQuarter) remain unchanged and continue to be used by the list view, which renders via React Native <Text> with proper platform font fallback.

Fixed Issues

$ #81952
PROPOSAL: #81952 (comment)

Tests

1. Set the app language to Chinese or Japanese
2. Open a workspace chat
3. Create a manual expense
4. Go to Reports > group by month > view as line chart
5. Verify that month labels on the x-axis display correctly as MM/YYYY format (e.g., 01/2026)
6. Switch to group by week and verify labels display as MM/DD/YYYY format
7. Switch to group by quarter and verify labels display as Q1 2026 format
8. Switch back to English and verify the chart labels still display correctly
9. Verify the list view still shows full localized month/week/quarter names

• Verify that no errors appear in the JS console

Offline tests

N/A - This change only affects label formatting in chart views, no network requests involved.

QA Steps

1. Set the app language to Chinese (简体中文) or Japanese (日本語)
2. Open a workspace chat and create a manual expense
3. Go to Reports and group by month, then switch to line chart view
4. Verify the x-axis labels display months in MM/YYYY numeric format
5. Repeat with group by week (expect MM/DD/YYYY format) and quarter (expect Q1 YYYY format)
6. Switch language back to English and verify charts still render correctly
7. Verify the list view (non-chart) still shows fully localized date strings

• 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
    • 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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[MelvinBot]

I created this PR from an upstream branch since I couldn't find a fork to push to.

To take ownership of this branch and be able to push updates, run:

git remote add upstream https://github.com/Expensify/App.git
git fetch upstream claude-fixCJKChartLabels
git checkout -b claude-fixCJKChartLabels upstream/claude-fixCJKChartLabels
git push -u origin claude-fixCJKChartLabels

Then you can close this PR and open a new one from your fork.

[MelvinBot]

Fixed the failing typecheck. The error was:

src/libs/ReportUtils.ts(13076,30): error TS2552: Cannot find name 'allReportsViolations'. Did you mean 'reportViolations'?

Root cause: The hasVisibleReportFieldViolations function (introduced by the merge of #84803) references a module-level variable allReportsViolations, but the corresponding Onyx.connect subscription for ONYXKEYS.COLLECTION.REPORT_VIOLATIONS was never added. This is a pre-existing bug on main, not caused by this PR's changes.

Fix: Added the missing Onyx connection for allReportsViolations following the same pattern as all other collection subscriptions in ReportUtils.ts.

[codecov]

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/libs/ReportUtils.ts	76.90% <100.00%> (+12.80%)	⬆️
src/components/Search/SearchChartView.tsx	5.55% <0.00%> (-0.83%)	⬇️
... and 147 files with indirect coverage changes

[MelvinBot]

Fixed the failing checks. The previous commit added the missing Onyx.connect for allReportsViolations in src/libs/ReportUtils.ts. The hasVisibleReportFieldViolations function referenced this module-level variable but the Onyx subscription that populates it was missing, causing both the TypeScript error (Cannot find name 'allReportsViolations') and the Jest test failure.

All checks are now passing (typecheck, ESLint, all 8 test jobs, builds, storybook, etc.). Only perf-tests is still running.