Skip to content

fix: backfill report actions when the newest page has none visible - #97689

Merged
mountiny merged 5 commits into
Expensify:mainfrom
callstack-internal:fix/backfill-report-actions-with-no-visible-page
Aug 7, 2026
Merged

mountiny merged 5 commits into
Expensify:mainfrom
callstack-internal:fix/backfill-report-actions-with-no-visible-page

Conversation

@BartekObudzinski

@BartekObudzinski BartekObudzinski commented Aug 3, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

The list renders the chain of report actions covered by the stored pagination page. If every action on that page is invisible, deleted expenses for example, the chain is empty and ReportActionsSkeletonGuard shows a skeleton instead of the list. That state cannot recover, because the list owns pagination and the list is what the skeleton replaced.

Reported for a self DM whose imported card expenses had all been deleted. The Onyx export shows one page covering 31 deleted expense actions, with 49 real messages cached but sitting outside it.

This adds useBackfillWhenNoVisibleActions, called from the skeleton guard. When the chain has no visible actions and older pages are still fetchable, it calls loadOlderChats and walks back until visible actions appear. MoneyRequestReportActionsList already does this for money request reports, which hit the same backend behaviour. Chats had no equivalent.

The loop is guarded. The cursor is the exact action ID loadOlderChats sends. Each cursor is requested once. A failed request re-arms that cursor once, so one transient failure does not strand the report. Offline and in flight requests block it.

If the walk reaches the start of history with nothing visible, the skeleton stays. That needs a defined terminal state and is tracked separately.

Fixed Issues

$ #97574
PROPOSAL:

Tests

The stored page has to cover only invisible actions. The backend produces that on its own but not on demand, so set it up directly.

  1. Open your self DM on web and send five messages.
  2. Staying in the report, run this in the console. Do not reload, OpenReport would overwrite the page.
(async () => {
    const id = window.location.pathname.match(/\/r\/(\d+)/)[1];
    const sorted = Object.values(await window.Onyx.get(`reportActions_${id}`)).sort((a, b) => {
        if (a.actionName === 'CREATED' && b.actionName !== 'CREATED') return 1;
        if (b.actionName === 'CREATED' && a.actionName !== 'CREATED') return -1;
        return a.created < b.created ? 1 : -1;
    });
    const hide = sorted.slice(0, 3).map((a) => a.reportActionID);
    const patch = {};
    for (const raid of hide) {
        patch[raid] = {message: [{type: 'COMMENT', html: '', text: '', deleted: '2026-08-04 07:00:00.000'}]};
    }
    await window.Onyx.merge(`reportActions_${id}`, patch);
    await window.Onyx.set(`reportActionsPages_${id}`, [['-1', ...hide]]);
})();
  1. On main, verify the report shows a skeleton and stays on it.
  2. On this branch, verify one GetOlderActions request goes out, the stored page grows past the three hidden actions, and the skeleton clears without a reload.
  • Verify that no errors appear in the JS console

Offline tests

  1. Go offline and run the setup above.
  2. Verify no GetOlderActions request is queued.
  3. Go back online and verify it runs once and the messages render.

QA Steps

The broken state comes from the backend returning a page made up entirely of invisible actions. It cannot be triggered on demand, only simulated locally, so there are no staging steps for it. Regression check instead:

  1. Open a few chats with history and verify they load their messages.
  2. Open a self DM containing expenses and verify it loads.
  3. Scroll up in a long chat and verify older messages still page in.
  • 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 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 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)
  • 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.
  • 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-08-04.at.09.41.35.mov

…-actions-with-no-visible-page

# Conflicts:
#	src/hooks/useReportActionsListModel.ts
@BartekObudzinski
BartekObudzinski marked this pull request as ready for review August 4, 2026 08:17
@BartekObudzinski
BartekObudzinski requested review from a team as code owners August 4, 2026 08:17
@melvin-bot
melvin-bot Bot requested review from gijoe0295 and trjExpensify and removed request for a team August 4, 2026 08:17
@melvin-bot

melvin-bot Bot commented Aug 4, 2026

Copy link
Copy Markdown

@gijoe0295 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 removed the request for review from a team August 4, 2026 08:17

@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: 7b8482fb2a

ℹ️ 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/hooks/useBackfillWhenNoVisibleActions.ts Outdated
@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

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

Minor comment cleanups

Comment thread src/selectors/ReportMetaData.ts Outdated
? {
hasOnceLoadedReportActions: loadingState.hasOnceLoadedReportActions,
isLoadingInitialReportActions: loadingState.isLoadingInitialReportActions,
// Read by the backfill that recovers a chain with no visible actions to render.

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.

Suggested change
// Read by the backfill that recovers a chain with no visible actions to render.

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.

Done


useMarkOpenReportEndOnSkeleton(report, shouldShowInitialSkeleton);

// The list owns pagination, so it can't recover a chain that renders as empty — it isn't mounted yet.

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.

Suggested change
// The list owns pagination, so it can't recover a chain that renders as empty — it isn't mounted yet.

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.

Done

Comment thread src/hooks/useLoadReportActions.ts Outdated
Comment on lines +142 to +144
// The exact cursor `loadOlderChats` sends. Exposed so callers that need to tell whether a request
// made progress compare against the ID that was actually requested, not against the rendered chain
// (which can end on a transaction thread action or a synthetic one that never reaches the server).

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.

Suggested change
// The exact cursor `loadOlderChats` sends. Exposed so callers that need to tell whether a request
// made progress compare against the ID that was actually requested, not against the rendered chain
// (which can end on a transaction thread action or a synthetic one that never reaches the server).

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.

Trimmed it to one line rather than dropping it. The cursor not matching the end of the rendered chain is what broke this hook while I was building it, so it is worth a note:

// The exact cursor `loadOlderChats` sends, which is not always the end of the rendered chain.

Comment on lines +24 to +26
* Whether the initial OpenReport call is still in flight. Must come from the request queue
* (`useIsReportLoadPending`), not from the RAM-only loading flag: a flag that never cleared would
* block the backfill for as long as the report stays open.

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.

Suggested change
* Whether the initial OpenReport call is still in flight. Must come from the request queue
* (`useIsReportLoadPending`), not from the RAM-only loading flag: a flag that never cleared would
* block the backfill for as long as the report stays open.
* Whether the initial OpenReport call is still in flight. Must come from the request queue (`useIsReportLoadPending`)

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.

Done

/** Whether the last GetOlderActions call failed */
hasLoadingOlderReportActionsError: boolean | undefined;

/** The cursor `loadOlderChats` sends, i.e. the oldest action of the current report */

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.

Suggested change
/** The cursor `loadOlderChats` sends, i.e. the oldest action of the current report */
/** The oldest action of the current report, i.e. the cursor `loadOlderChats` sends */

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.

Done

const previousReportIDRef = useRef(reportID);

useEffect(() => {
// A different report gets its own cursor, otherwise the guard could carry over an ID this report never requested.

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.

Suggested change
// A different report gets its own cursor, otherwise the guard could carry over an ID this report never requested.

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.

Done

Comment on lines +14 to +16
* If the report has newer actions to load. Only the newest chain is backfilled: a chain anchored on a
* linked or unread action sits in the middle of the history, so walking backwards from it could page
* through everything older while the visible actions sit on the newer side.

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.

Suggested change
* If the report has newer actions to load. Only the newest chain is backfilled: a chain anchored on a
* linked or unread action sits in the middle of the history, so walking backwards from it could page
* through everything older while the visible actions sit on the newer side.
* If the report has newer actions to load

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.

Done

Comment thread src/hooks/useBackfillWhenNoVisibleActions.ts
Comment on lines +81 to +83
// A failed request consumes the cursor without advancing it, so without this one transient failure
// would strand the report on the skeleton — the symptom this hook exists to fix. Each cursor gets a
// single retry, so a request that keeps failing can't spin.

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.

Suggested change
// A failed request consumes the cursor without advancing it, so without this one transient failure
// would strand the report on the skeleton — the symptom this hook exists to fix. Each cursor gets a
// single retry, so a request that keeps failing can't spin.
// A failed request consumes the cursor without advancing it.
// Each cursor gets a single retry, so a request that keeps failing can't block.

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.

Done, kept your wording but with "spin" instead of "block". The risk there is a repeating request loop rather than the backfill getting stuck.

Comment on lines +93 to +94
// Safety guard against an infinite request loop: if the cursor hasn't advanced since the last
// call, the server has no more actions to give us for this chain.

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.

Suggested change
// Safety guard against an infinite request loop: if the cursor hasn't advanced since the last
// call, the server has no more actions to give us for this chain.
// If the cursor hasn't advanced since the last call, the server has no more actions for this chain.

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.

Done

@gijoe0295

gijoe0295 commented Aug 4, 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-08-07.at.01.27.55.mov
Android: mWeb Chrome
iOS: HybridApp
Screen.Recording.2026-08-07.at.00.36.08.mov
iOS: mWeb Safari
Screen.Recording.2026-08-07.at.00.37.23.mov
MacOS: Chrome / Safari
Screen.Recording.2026-08-06.at.23.52.08.mov

@gijoe0295

Copy link
Copy Markdown
Contributor

The backend produces that on its own but not on demand

@BartekObudzinski I'm not crystal-clear on this point. Can't we create several expenses then delete them? The number of deleted expenses should be large enough to cover a page? I think we can try to come up with manual test steps for this.

@BartekObudzinski

Copy link
Copy Markdown
Contributor Author

Verified the fix itself: with the stored page pointed at only invisible actions, main stays on the skeleton, and this branch fires one GetOlderActions, merges the pages and renders the messages. That is the local test in the Tests section.

The expense route does not reproduce though. I tried 60+ messages deleted, then a fresh sign in, and got no skeleton. The reporter was deleting tracked expenses rather than messages, and the backend picks the OpenReport window, so we cannot force it to land entirely on invisible actions.

@BartekObudzinski

Copy link
Copy Markdown
Contributor Author

@gijoe0295 can be rerevied

@BartekObudzinski

Copy link
Copy Markdown
Contributor Author

@gijoe0295 How is the review going?

@gijoe0295

Copy link
Copy Markdown
Contributor

Testing. Should be done soon

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

@melvin-bot
melvin-bot Bot requested a review from mountiny August 6, 2026 18:31
@mountiny

mountiny commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

GH actions are not working now

@mountiny mountiny closed this Aug 7, 2026
@mountiny mountiny reopened this Aug 7, 2026

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

I think the comment is not strictly correct there, can you please update it in a follow up? I dont want to hold this PR on the comment so we can fix real bug users can hit sooner than later

};

/**
* Loads older chats in a report whose newest page contains no visible actions.

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.

Suggested change
* Loads older chats in a report whose newest page contains no visible actions.
* Loads older report actions in a report whose newest page contains no visible actions.

/**
* Loads older chats in a report whose newest page contains no visible actions.
*
* The backend prioritizes IOU actions in OpenReport, so a report can come back with a page made up

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 don think it prioritizes the IOU report actions, the actions are all sent in the order in which they had been created so in this case its latest 50 report actions are invisible, if you would send a comment that would be fixed I think

Suggested change
* The backend prioritizes IOU actions in OpenReport, so a report can come back with a page made up
* A report can come back with a page made up

@mountiny
mountiny merged commit 3d08f45 into Expensify:main Aug 7, 2026
43 of 45 checks passed
@OSBotify

OSBotify commented Aug 7, 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.

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.4.52-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 I reviewed the changes in this PR against Expensify's help site content under App/docs/articles.

No help site changes are required. ✅

This PR is an internal bug fix — it adds useBackfillWhenNoVisibleActions so a report whose stored pagination page contains only invisible actions (e.g. all deleted expenses) walks back through older pages and recovers, instead of getting stuck on a ReportActionsSkeletonGuard skeleton that can never clear.

Why no docs update is needed
  • The changed files are all internal logic and tests — src/hooks/useBackfillWhenNoVisibleActions.ts, src/hooks/useLoadReportActions.ts, src/hooks/useReportActionsListModel.ts, src/pages/inbox/report/ReportActionsSkeletonGuard.tsx, src/selectors/ReportMetaData.ts, and their tests.
  • There are no new user-facing features, settings, tabs, buttons, UI labels, or copy changes.
  • The fix restores expected behavior (messages load instead of an infinite skeleton). Help articles document what users can do and how features work — none of that changes here, so there is no article to add or edit.

Since no documentation change is warranted, no draft help site PR was created — there is nothing to review on the docs side.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/roryabraham in version: 9.4.52-11 🚀

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.

6 participants