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 2026-01-16] [$250] Expensify card - RHP back button on Success page after deactivating card opens not here page #75178
What changes do you think we should make in order to solve the problem?
We should navigate to SETTINGS_WALLET_DOMAIN_CARD with newCardID if it exists
const handleBackButtonPress = () => {
if (isReasonConfirmed) {
setIsReasonConfirmed(false);
return;
}
Navigation.goBack(ROUTES.SETTINGS_WALLET_DOMAIN_CARD.getRoute(newCardID ?? cardID)); // or we should call navigate with `newCardID`
};
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
changed the title [-]Expensify card - RHP back button on Success page after deactivating card opens not here page[/-][+][$250] Expensify card - RHP back button on Success page after deactivating card opens not here page[/+]on Nov 18, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.96-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@truph01@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]
[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:
[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:
[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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Create an Expensify card in a workspace
Assign a physical card
Go to the Wallet page
Click on the card
Click on the assigned card
Click on the ‘Report physical card loss/damage’
Select any reason > Next.
Click Deactivate card.
Enter magic code.
Verify that: in success page. we have the header back button
Click to the header back button
Verify that: RHP back button on Success page will open card details page.
Do we agree 👍 or 👎
Activity
melvin-bot commentedon Nov 14, 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.daledah commentedon Nov 14, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
RHP back button on Success page after deactivating card opens not here page.
What is the root cause of that problem?
After we deactivate the card success, we are navigating to
SETTINGS_WALLET_DOMAIN_CARDagain with the oldcardID=> not found page is shownApp/src/pages/settings/Wallet/ReportCardLostPage.tsx
Lines 147 to 154 in cecf68a
What changes do you think we should make in order to solve the problem?
We should navigate to
SETTINGS_WALLET_DOMAIN_CARDwithnewCardIDif it existsWhat alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
melvin-bot commentedon Nov 18, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021990787728697448217
[-]Expensify card - RHP back button on Success page after deactivating card opens not here page[/-][+][$250] Expensify card - RHP back button on Success page after deactivating card opens not here page[/+]melvin-bot commentedon Nov 18, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @truph01 (
External)30 remaining items
melvin-bot commentedon Jan 9, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.96-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 2026-01-16. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jan 9, 2026
@truph01 @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]
bfitzexpensify commentedon Jan 16, 2026
Payment complete to @daledah
@truph01 please complete the BZ checklist
bfitzexpensify commentedon Jan 19, 2026
Bump @truph01
truph01 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:
[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:
[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.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
bfitzexpensify commentedon Jan 20, 2026
Payment summary:
@truph01 due $250 for PR review via NewDot manual request
JmillsExpensify commentedon Apr 5, 2026
$250 approved for @truph01