You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Report - App returns to workspace chat when open report offline & return online, skeleton loader shown #71837
Version Number: 9.2.23-0 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail:#71190 Email or phone of affected tester (no customers):joinsjdoisnodnsjio@gmail.com Issue reported by: Applause - Internal Team
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat
Go offline
Click + > Create report
Open the new report
Go online
Open the empty report
Go offline
Go online
Expected Result:
In Step 6, app will stay on the report after create new report offline, open the report and return online
In Step 9, report will not turn to skeleton loader when returning online
Actual Result:
In Step 6, app returns to workspace chat after create new report offline, open the report and return online
In Step 9, report turns to skeleton loader when returning online
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6964107_1759522112821.Screen_Recording_2025-10-04_at_04.08.00.mp4
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
Activity
melvin-bot commentedon Oct 3, 2025
Triggered auto assignment to @JmillsExpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Oct 3, 2025
Triggered auto assignment to @dangrous (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Oct 3, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Oct 3, 2025
💬 A slack conversation has been started in #expensify-open-source
izarutskaya commentedon Oct 6, 2025
Issue is still reproducible on Windows 10/Chrome and
Samsung Galaxy A40/Android 11/App with Ad-hoc Build v9.2.23-0
2025-10-06.14-15-32.mp4
mobizen_20251006_143638.mp4
22 remaining items
github-actions commentedon Oct 6, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
lakchote commentedon Oct 6, 2025
Putting the label back as the CP to Staging for the revert has some failures. https://github.com/Expensify/App/actions/runs/18287000365/job/52064602529
lakchote commentedon Oct 6, 2025
CP to staging was successful actually so removing the label.
lakchote commentedon Oct 7, 2025
@ikevin127 please check @DylanDylann comment here, thanks
ikevin127 commentedon Oct 8, 2025
DylanDylann commentedon Oct 8, 2025
The offending PR was reverted, let's close this issue