Repository navigation
[Due for payment 2026-01-21] Company card - RHP shows not here page briefly after Unassign card #78319
Description
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.2.86-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #78069
Email or phone of affected tester (no customers): sndoijsoinjdiisjdiosj@gmail.co
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Money Requests
Action Performed:
Precondition:
- Workspace has company cards.
- Go to staging.new.expensify.com
- Go to workspace settings > Company cards.
- Assign a card to yourself.
- Click on the card.
- Click Unassign card.
- Unassign the card.
Expected Result:
RHP will not show not here page after Unassign card.
Actual Result:
RHP shows not here page briefly after Unassign card.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
Activity
melvin-bot commentedon Dec 23, 2025
You have been assigned to this deploy blocker because you recently merged this PR: #78069
melvin-bot commentedon Dec 23, 2025
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Dec 23, 2025
Triggered auto assignment to @bfitzexpensify (
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.github-actions commentedon Dec 23, 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:
44 remaining items
melvin-bot commentedon Jan 14, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 14, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.1-1 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 2026-01-21. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jan 14, 2026
@hungvu193 / @ikevin127 @bfitzexpensify 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]
hungvu193 commentedon Jan 19, 2026
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: This is a known issue that came from Tgolen fix transition #78078. We decided to fix it as a follow up here.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
bfitzexpensify commentedon Jan 26, 2026
Payment summary:
@hungvu193 due $250 through NewDot Manual Requests
@ikevin127 due $250 through NewDot Manual Requests
garrettmknight commentedon Jan 26, 2026
$250 approved for @ikevin127
twisterdotcom commentedon Jan 27, 2026
@hungvu193 has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-8074-a41d-553e-ae743a745884