[CP Staging] fix: Invoice report loading infinitely by chrispader · Pull Request #90323 · Expensify/App

chrispader · 2026-05-12T10:14:17Z

@rlinoz

Explanation of Change

Fixes an issue where reports would not load while offline after #90072 has been merged.

Fixed Issues

$ #90293
$ #90287
PROPOSAL:

Tests

Verify that no errors appear in the JS console

Expense details loading infitely

Prerequisite: Account has at least one workspace.

Open the staging.new.expensify.com website.
Open any workspace chat.
Create a new empty report.
Turn off internet connection.
Open the just created report and click on "Add Expense"
Add a new manual expense.
Note that after expense is created, receipt thumbnail is visible (On Web), but expense details load infinitely.
Turn on internet connection
Note that now, expense details load correctly.

Invoice report loading infinitely

Precondition:

Invoice is enabled.
Go to staging.new.expensify.com
Go offline.
Open FAB > Send invoice.
Send invoice to any user.
Open the invoice report.

Offline tests

The above tests are for offline behavior.

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Verify that no errors appear in the JS console

Same as in Tests.

PR Author Checklist

Screenshots/Videos

MacOS: Chrome / Safari

Screen.Recording.2026-05-12.at.11.12.59.mov

Screen.Recording.2026-05-12.at.11.33.20.mov

melvin-bot · 2026-05-12T10:14:25Z

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

abzokhattab · 2026-05-12T11:18:31Z

I am trying to reproduce this issue first on main #90287 but i am not able to reproduce it following the steps

Screen.Recording.2026-05-12.at.14.02.22.mov

But I was able to reproduce the other blocker #90293 and the change does fixes it

Before

Screen.Recording.2026-05-12.at.14.15.38.mov

After

Screen.Recording.2026-05-12.at.14.14.53.mov

abzokhattab · 2026-05-12T11:25:36Z

nvm i was able to reproduce the first issue on ios

abzokhattab · 2026-05-12T12:02:02Z

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

Screen.Recording.2026-05-12.at.14.44.43.mov

Screen.Recording.2026-05-12.at.14.47.40.mov

Android: mWeb Chrome

Screen.Recording.2026-05-12.at.14.52.49.mov

Screen.Recording.2026-05-12.at.14.53.26.mov

iOS: HybridApp

Screen.Recording.2026-05-12.at.14.23.00.mov

Screen.Recording.2026-05-12.at.14.24.22.mov

iOS: mWeb Safari

Screen.Recording.2026-05-12.at.14.26.01.mov

Screen.Recording.2026-05-12.at.14.27.11.mov

MacOS: Chrome / Safari

Screen.Recording.2026-05-12.at.14.16.43.mov

Screen.Recording.2026-05-12.at.14.50.20.mov

abzokhattab

LGTM .. both issues were fixed

Beamanator · 2026-05-12T13:55:02Z

thanks for the fix!!

…-loading-infinitely-while-offline [CP Staging] fix: Invoice report loading infinitely (cherry picked from commit 6389ba3) (cherry-picked to staging by Beamanator)

OSBotify · 2026-05-12T14:04:23Z

✋ 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 · 2026-05-12T14:16:57Z

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

github-actions · 2026-05-12T14:23:26Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-6389ba3-e9e8cfb-9cdd009f540817d558d58c83786c2dc13cbb5942/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-6389ba3-e9e8cfb-ad19f9f27bf1d879bf206f420d5fa30039612fae/index.html

Web 🕸️
https://90323.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-05-12T14:38:15Z

🚀 Cherry-picked to staging by https://github.com/Beamanator in version: 9.3.70-3 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-05-12T14:40:56Z

No help site changes are required for this PR. This is a technical bug fix that adjusts offline loading logic in ReportActionsView.tsx — no user-facing features, terminology, settings, or workflows were added or changed.

OSBotify · 2026-05-13T01:21:59Z

🚀 Cherry-picked to staging by https://github.com/Beamanator in version: 9.3.72-0 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-05-13T01:23:06Z

No help site changes are needed for this PR. The change is an internal bug fix to ReportActionsView.tsx that resolves infinite loading states while offline — it doesn't introduce new features, rename UI elements, or change any user-facing flows documented on the help site.

OSBotify · 2026-05-13T07:03:17Z

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.72-1 🚀

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

OSBotify · 2026-05-13T07:25:52Z

🚀 Cherry-picked to staging by https://github.com/Beamanator in version: 9.3.73-0 🚀

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

Bundle Size Analysis (Sentry):

iOS

OSBotify · 2026-05-13T07:56:48Z

🚀 Cherry-picked to staging by https://github.com/Beamanator in version: 9.3.73-0 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

fix: invoice report loading infinitely

8773700

chrispader requested review from a team as code owners May 12, 2026 10:14

melvin-bot Bot assigned chrispader May 12, 2026

melvin-bot Bot requested review from ShridharGoel and joekaufmanexpensify and removed request for a team May 12, 2026 10:14

mountiny changed the title ~~fix: Invoice report loading infinitely~~ [CP Staging] fix: Invoice report loading infinitely May 12, 2026

mountiny requested review from abzokhattab and removed request for ShridharGoel May 12, 2026 10:20

chrispader mentioned this pull request May 12, 2026

feat: Open reports at first unread action V2 #90072

Merged

50 tasks

abzokhattab approved these changes May 12, 2026

View reviewed changes

melvin-bot Bot requested a review from mountiny May 12, 2026 12:02

Beamanator approved these changes May 12, 2026

View reviewed changes

Beamanator merged commit 6389ba3 into Expensify:main May 12, 2026
51 checks passed

OSBotify added the CP Staging marks PRs that have been CP'd to staging label May 12, 2026

OSBotify mentioned this pull request May 12, 2026

Deploy Checklist: New Expensify 2026-05-11 #90263

Closed

This was referenced May 13, 2026

[Due for payment 2026-05-20] Invoice - Invoice report loads infinitely when sent offline #90293

Closed

[Due for payment 2026-05-20] Report - Expense details load infinitelly after adding expense to empty report offline. #90287

Closed

Conversation

chrispader commented May 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot Bot commented May 12, 2026

Uh oh!

abzokhattab commented May 12, 2026

Uh oh!

abzokhattab commented May 12, 2026

Uh oh!

abzokhattab commented May 12, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

abzokhattab left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Beamanator commented May 12, 2026

Uh oh!

OSBotify commented May 12, 2026

Uh oh!

github-actions Bot commented May 12, 2026

Uh oh!

github-actions Bot commented May 12, 2026

Uh oh!

OSBotify commented May 12, 2026

Uh oh!

MelvinBot commented May 12, 2026

Uh oh!

OSBotify commented May 13, 2026

Uh oh!

MelvinBot commented May 13, 2026

Uh oh!

OSBotify commented May 13, 2026

Uh oh!

OSBotify commented May 13, 2026

Uh oh!

OSBotify commented May 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

chrispader commented May 12, 2026 •

edited

Loading