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-10-01] [Due for payment 2025-09-04] Reports - Distance expense created while on "Reports" doesn´t appear automatically #69086
Prerequisite: Account has at least one workspace available
Prerequisite 2: No expenses created yet
Open the staging.new.expensify.com website
Navigate to "Reports"
Tap on FAB and select "Create Expense"
Complete a distance expense creation flow
When landing on "Reports" again, note that new expense appears briefly and then empty state screen appears again
Expected Result:
New created expense should appear automatically on "Reports"
Actual Result:
When creating a new distance expense on "Reports" via FAB, the expense doesn´t automatically appear on expenses list. When finishing the creation flow, expense can be briefly seen, and then empty state screen appears again. Expense only appears after navigating to a different section and returning to "Reports"
Issue is reproducible in any section of "Reports"
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 evidenceBug6924210_1755894160765.Distance.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.
changed the title [-][Due for payment 2025-09-04] Reports - Distance expense created while on "Reports" doesn´t appear automatically[/-][+][Due for payment 2025-10-01] [Due for payment 2025-09-04] Reports - Distance expense created while on "Reports" doesn´t appear automatically[/+]on Sep 24, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.17-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@neil-marcellini 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 22, 2025
Triggered auto assignment to @johncschuster (
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 22, 2025
Triggered auto assignment to @neil-marcellini (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Aug 22, 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 22, 2025
💬 A slack conversation has been started in #expensify-open-source
lanitochka17 commentedon Aug 22, 2025
Production:
fa6.mp4
neil-marcellini commentedon Aug 25, 2025
I'm looking into the root cause
14 remaining items
melvin-bot commentedon Sep 23, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Sep 24, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
[-][Due for payment 2025-09-04] Reports - Distance expense created while on "Reports" doesn´t appear automatically[/-][+][Due for payment 2025-10-01] [Due for payment 2025-09-04] Reports - Distance expense created while on "Reports" doesn´t appear automatically[/+]melvin-bot commentedon Sep 24, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Sep 24, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.17-6 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-10-01. 🎊
melvin-bot commentedon Sep 24, 2025
@neil-marcellini 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]