Skip to content

Fix Report- Something when wrong when resize to fullscreen in bar or line view of expense report#87084

Merged
puneetlath merged 18 commits intoExpensify:mainfrom
software-mansion-labs:borys3kk-fix-something-went-wrong-charts
Apr 21, 2026
Merged

Fix Report- Something when wrong when resize to fullscreen in bar or line view of expense report#87084
puneetlath merged 18 commits intoExpensify:mainfrom
software-mansion-labs:borys3kk-fix-something-went-wrong-charts

Conversation

@borys3kk
Copy link
Copy Markdown
Contributor

@borys3kk borys3kk commented Apr 3, 2026

Explanation of Change

Fixed chart crashes caused by excessive re-renders. Moved activeDataIndex and isOverClickableTarget from React state to Reanimated SharedValues so hover/cursor changes no longer trigger React re-renders. Extracted ChartTooltipLayer to read shared values directly. Refactored useChartLabelLayout to return label widths only; truncation is now handled during render in ChartXAxisLabels. Added useChartLabelMeasurements, useChartParagraphs, and useYAxisLabelWidth hooks.

Fixed Issues

$ #87066

PROPOSAL:

Tests

Crash fix:

  1. Go to reports tab
  2. Select type:expense
  3. Select group-by:merchant
  4. Resize window in multiple times
  5. Maximize the window
  6. Ensure that no crash occurs
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as tests

// TODO: These must be filled out, or the issue title must include "[No 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
      • 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 image
Android: mWeb Chrome image
iOS: Native image
iOS: mWeb Safari image
MacOS: Chrome / Safari
Screen.Recording.2026-04-03.at.16.06.23.mov

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 3, 2026

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 Δ
...omponents/Charts/hooks/useChartInteractionState.ts 100.00% <100.00%> (+28.57%) ⬆️
src/components/Charts/hooks/useChartLabelLayout.ts 100.00% <100.00%> (ø)
...mponents/Charts/hooks/useChartLabelMeasurements.ts 100.00% <100.00%> (ø)
.../components/Charts/components/ChartYAxisLabels.tsx 0.00% <0.00%> (ø)
src/components/Charts/hooks/useLabelHitTesting.ts 0.00% <0.00%> (ø)
...components/Charts/components/ChartTooltipLayer.tsx 0.00% <0.00%> (ø)
src/components/Charts/hooks/useYAxisLabelWidth.ts 0.00% <0.00%> (ø)
src/components/Charts/hooks/useChartParagraphs.ts 0.00% <0.00%> (ø)
.../components/Charts/components/ChartXAxisLabels.tsx 0.00% <0.00%> (ø)
src/components/Charts/BarChart/BarChartContent.tsx 5.00% <0.00%> (-0.36%) ⬇️
... and 3 more
... and 297 files with indirect coverage changes

Comment thread src/components/Charts/components/ChartTooltipLayer.tsx Outdated
Copy link
Copy Markdown
Contributor

@mhawryluk mhawryluk left a comment

Choose a reason for hiding this comment

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

Awesome! 🚀

@borys3kk borys3kk marked this pull request as ready for review April 3, 2026 14:55
@borys3kk borys3kk requested review from a team as code owners April 3, 2026 14:55
@melvin-bot melvin-bot Bot requested review from DylanDylann and removed request for a team April 3, 2026 14:55
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 3, 2026

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

Copy link
Copy Markdown

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

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: 4c976df66b

ℹ️ 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/components/Charts/components/ChartTooltipLayer.tsx
Copy link
Copy Markdown
Contributor

@joekaufmanexpensify joekaufmanexpensify left a comment

Choose a reason for hiding this comment

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

Fix is good for product

@borys3kk
Copy link
Copy Markdown
Contributor Author

borys3kk commented Apr 7, 2026

hi @DylanDylann, how's the review coming along?

@DylanDylann
Copy link
Copy Markdown
Contributor

On my list today

@DylanDylann
Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown

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

ℹ️ 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".

@DylanDylann
Copy link
Copy Markdown
Contributor

@borys3kk I think this bug only reproduces on Windows; unfortunately, I don’t have it. Could you ask someone to verify it there? Otherwise, we should ask the QA team to test this PR using an ad-hoc build.

@borys3kk
Copy link
Copy Markdown
Contributor Author

borys3kk commented Apr 7, 2026

@borys3kk I think this bug only reproduces on Windows; unfortunately, I don’t have it. Could you ask someone to verify it there? Otherwise, we should ask the QA team to test this PR using an ad-hoc build.

I was also able to reproduce this bug on macOS so I think you're good to go

@DylanDylann
Copy link
Copy Markdown
Contributor

@borys3kk The code change looks fine to me

Could you update and add unit tests?

src/components/Charts/utils.ts 61.90% <0.00%> (-5.34%) ⬇️

@borys3kk
Copy link
Copy Markdown
Contributor Author

borys3kk commented Apr 7, 2026

@borys3kk The code change looks fine to me

Could you update and add unit tests?

src/components/Charts/utils.ts 61.90% <0.00%> (-5.34%) ⬇️

sure, on it

@DylanDylann
Copy link
Copy Markdown
Contributor

Reviewing now....

@DylanDylann
Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Something went wrong. Try again later by commenting “@codex review”.

We were unable to download your code in a timely manner.
ℹ️ 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".

@DylanDylann
Copy link
Copy Markdown
Contributor

Manual useMemo is redundant with React Compiler

@DylanDylann
Copy link
Copy Markdown
Contributor

useChartLabelMeasurements is called twice, in both chart content components call useChartLabelMeasurements directly AND implicitly via useChartLabelLayout which calls it internally

@DylanDylann
Copy link
Copy Markdown
Contributor

I discovered a new bug (also happens on the main branch). We can consider fixing in a new PR

I can't scroll down the chart in mWeb

Screen.Recording.2026-04-17.at.15.42.56.mov

@DylanDylann
Copy link
Copy Markdown
Contributor

@MelvinBot Could you review this change?

@MelvinBot
Copy link
Copy Markdown
Contributor

🤖 Code Review

The core approach is sound — moving activeDataIndex and isOverClickableTarget from React state to Reanimated SharedValues eliminates the React re-render cascade on every hover event, which fixes the crash. The ChartTooltipLayer isolation is a clean pattern. A few items to address:

1. useChartLabelMeasurements is called twice per chart (as DylanDylann noted)

Both BarChartContent and LineChartContent call useChartLabelMeasurements directly and useChartLabelLayout calls it internally. Same arguments (data, fontMgr, fontSize). React's hook rules mean these are independent hook instances, so the Skia text measurements run twice per render.

Options: (a) have useChartLabelLayout accept the measurements as a parameter instead of calling the hook internally, or (b) remove the direct call in the chart content components and derive labelWidths/ellipsisWidth from useChartLabelLayout's return value.

2. Explicit useMemo with React Compiler (as DylanDylann noted)

The App uses React Compiler, which auto-memoizes. The explicit useMemo calls in useChartLabelMeasurements, useChartParagraphs, useYAxisLabelWidth, ChartXAxisLabels, and ChartYAxisLabels are functionally redundant. They won't cause bugs, but removing them would align with the codebase convention and reduce noise.

3. builderCache WeakMap — verify reset() is safe across Skia versions

The ParagraphBuilder reuse via builderCache and reset() is a nice optimization. Just want to flag: reset() on SkParagraphBuilder clears internal state but the method availability can vary across @shopify/react-native-skia versions. Worth confirming it's available in the version pinned in package.json.

4. Minor: GLYPH_PADDING / 2GLYPH_PADDING change

In both BarChartContent and LineChartContent, the left padding calculation changed from yAxisLabelWidth + GLYPH_PADDING / 2 to yAxisLabelWidth + GLYPH_PADDING, and similarly in ChartYAxisLabels the x-position and width calculations changed. This doubles the effective glyph padding. Was this intentional to fix a visual alignment issue, or an oversight?


Overall this is a well-structured fix for the re-render problem. The SharedValue approach correctly keeps hover events on the UI thread, and the ChartTooltipLayer isolation ensures only the tooltip re-renders when the active index changes. Items 1 and 2 are the main actionable ones.

@borys3kk
Copy link
Copy Markdown
Contributor Author

@DylanDylann fixed both comments

@borys3kk
Copy link
Copy Markdown
Contributor Author

I discovered a new bug (also happens on the main branch). We can consider fixing in a new PR

I can't scroll down the chart in mWeb

Screen.Recording.2026-04-17.at.15.42.56.mov

I can look at it but I also think that it should be fixed in a new PR

@DylanDylann
Copy link
Copy Markdown
Contributor

@borys3kk Please fix the failed checks

@DylanDylann
Copy link
Copy Markdown
Contributor

@codex review

Copy link
Copy Markdown

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

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: 774e9ca583

ℹ️ 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".

<ChartXAxisLabels
labels={truncatedLabels}
labels={originalLabels}
labelWidths={truncatedLabelWidths}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Pass original widths to X-axis label truncation

ChartXAxisLabels expects labelWidths to be the measured widths of the original labels, because it decides whether to truncate by checking labelWidth <= maxWidth before calling truncateLabel(). Passing truncatedLabelWidths here (already clamped in useChartLabelLayout) makes many overlong labels look like they already fit, so they render untruncated and can overflow/overlap, while hit-testing still uses the clamped geometry. The same wiring is present in LineChartContent as well.

Useful? React with 👍 / 👎.

@borys3kk
Copy link
Copy Markdown
Contributor Author

@DylanDylann all yours

Copy link
Copy Markdown
Contributor

@DylanDylann DylanDylann left a comment

Choose a reason for hiding this comment

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

LGTM

@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 21, 2026

We did not find an internal engineer to review this PR, trying to assign a random engineer to #87066 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 puneetlath April 21, 2026 11:29
Copy link
Copy Markdown
Contributor

@puneetlath puneetlath left a comment

Choose a reason for hiding this comment

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

Good job with this.

One piece of feedback: there's a lot going on in this PR and I found it difficult to keep it all in-context. I think I could've done a better review if it had been smaller. Would it have been possible to break this up into some smaller PRs instead of one big one?

@puneetlath puneetlath merged commit 8a6f5bb into Expensify:main Apr 21, 2026
35 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

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

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

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.3.62-0 🚀

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

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.

8 participants