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
Expense - Missing composer after simultaneously submit&receive expense offline and return online #68805
[User B] While online, submit an expense to User A
[User A] Go online
Expected Result:
After returning online, 1:1 DM with User B will show the composer
Actual Result:
After returning online, 1:1 DM with User B does not show the composer.
The report is also not highlighted in LHN.
URL shows https://staging.new.expensify.com/r
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 evidenceBug6921469_1755640505808.Screen_Recording_2025-08-20_at_05.51.48.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.
Still can't reliably reproduce, but looking at the code, it's most likely this PR causing the problem: #68527
It changed the route fetching and now runs inside a strict guard that requires the active route to include the optimistic ID. If the user is on generic /r, the guard skips reroute entirely, the optimistic report gets cleared, and you’re left on /r with no composer and no LHN highlight.
I'm doing an ad hoc build with reverted #68527 in this PR: #68917 - I'll ask QA to test that so we know for sure if the error is caused by that particular PR.
Activity
melvin-bot commentedon Aug 19, 2025
Triggered auto assignment to @mallenexpensify (
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 19, 2025
Triggered auto assignment to @mjasikowski (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 19, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Aug 19, 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:
lanitochka17 commentedon Aug 19, 2025
Production:
Recording.3643.mp4
mallenexpensify commentedon Aug 20, 2025
hmm.. wasn't able to reproduce, and/or.. I see the composer in the vid above, as well as mine
2025-08-19_17-38-09.mp4
mjasikowski commentedon Aug 20, 2025
Can't reproduce either. @lanitochka17 can you please re-test?
lanitochka17 commentedon Aug 20, 2025
@mjasikowski The issue is reproduced with new accounts.
lanitochka17 commentedon Aug 20, 2025
issue is reproducible on mWeb too
ScreenRecording_08-21-2025.00-15-17_1.MP4
IuliiaHerets commentedon Aug 20, 2025
@mjasikowski QA team can repro this issue on Desktop, mWeb/Chrome and iOS app
https://github.com/user-attachments/assets/50b62100-536b-4836-ab94-7bfb8d968144
https://github.com/user-attachments/assets/2f5eb3a9-879b-45c6-b738-752609798545
https://github.com/user-attachments/assets/44e7e369-eee4-416f-b016-e289540fbc93
but not repro on Mac/Chrome and Android app
https://github.com/user-attachments/assets/ca025202-21c9-461f-9cb0-bf48994c1038
https://github.com/user-attachments/assets/0923ca6e-29d3-4efb-b2bf-e863e71fa27e
rushatgabhane commentedon Aug 20, 2025
@BlameGPT find offending PRs
BlameGPT commentedon Aug 20, 2025
Lowkey sus PRs fr fr
If not above, check these
mallenexpensify commentedon Aug 20, 2025
Thanks @rushatgabhane , @mjasikowski , do any of those look like the culprit?
mjasikowski commentedon Aug 21, 2025
Trying again, and:
Can't reproduce on mac/firefox.
Can't reproduce on mWeb on my iPhone.
mjasikowski commentedon Aug 21, 2025
Still can't reliably reproduce, but looking at the code, it's most likely this PR causing the problem: #68527
It changed the route fetching and now runs inside a strict guard that requires the active route to include the optimistic ID. If the user is on generic /r, the guard skips reroute entirely, the optimistic report gets cleared, and you’re left on /r with no composer and no LHN highlight.
mjasikowski commentedon Aug 21, 2025
I'm doing an ad hoc build with reverted #68527 in this PR: #68917 - I'll ask QA to test that so we know for sure if the error is caused by that particular PR.
mjasikowski commentedon Aug 21, 2025
Ad hoc build ready, asked QA for a re-test: https://expensify.slack.com/archives/C9YU7BX5M/p1755781959411029
mjasikowski commentedon Aug 22, 2025
The offending PR was reverted, closing this for now until it resurfaces.