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
[Due for payment 2025-08-15] Reports - Expense submitted offline, doesn´t appear until turning internet connection on. #67843
Prerequisite: Account has at least one workspace.
Prerequisite 2: Account has no expense yet.
Open the Expensify app.
Navigate to "Reports"
Force offline from the app´s troubleshoot.
Tap on "Create Expense" on the empty state modal.
Create a manual expense.
Once redirected to "Reports" again, note that the just created expense appears and disappears, and empty state modal remains displayed.
Turn on internet connection.
Note that a "Something went wrong" error message appears.
Expected Result:
When creating an expense while offline on "Reports", empty state modal should disappear and expense should appear with reduced opacity.
Actual Result:
Expense created on "Reports" after forcing offline mode on app, doesn´t appear and empty state modal remains displayed. When turning internet connection on again, a "Something went wrong" screen appears.
👋 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.
changed the title [-]Reports - Expense submitted offline, doesn´t appear until turning internet connection on.[/-][+][Due for payment 2025-08-15] Reports - Expense submitted offline, doesn´t appear until turning internet connection on.[/+]on Aug 8, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.90-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@luacmartins / @neil-marcellini@adelekennedy The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Aug 5, 2025
Triggered auto assignment to @adelekennedy (
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 Aug 5, 2025
Triggered auto assignment to @neil-marcellini (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Aug 5, 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 Aug 5, 2025
💬 A slack conversation has been started in #expensify-open-source
neil-marcellini commentedon Aug 5, 2025
Looking into this now
8 remaining items
luacmartins commentedon Aug 6, 2025
This was fixed via CP.
luacmartins commentedon Aug 6, 2025
No payment due. Closing.
[-]Reports - Expense submitted offline, doesn´t appear until turning internet connection on.[/-][+][Due for payment 2025-08-15] Reports - Expense submitted offline, doesn´t appear until turning internet connection on.[/+]melvin-bot commentedon Aug 8, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Aug 8, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.90-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-08-15. 🎊
melvin-bot commentedon Aug 8, 2025
@luacmartins / @neil-marcellini @adelekennedy The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]