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-03-21] Close account - App opens Debug console page after closing account #57341
Version Number: 9.1.5-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers):mojosjdosjsodi@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.3 / Chrome App Component: Other
Action Performed:
Go to staging.new.expensify.com
Go to Security > Close account.
Enter email in email field.
Click Close account.
Click Yes, continue.
Expected Result:
App will return to login page.
Actual Result:
App opens Debug console page after closing account.
👋 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.
@bfitzexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
@stitesExpensify what are your thoughts on re: being a blocker (in which case we should revert) vs. removing the blocker label and fixing it? I think it's not a flow that's worth blocking deployment IMO, but not super serious about it :P
changed the title [-]Close account - App opens Debug console page after closing account[/-][+][Due for payment 2025-03-21] Close account - App opens Debug console page after closing account[/+]on Mar 14, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.12-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@carlosmiceli / @stitesExpensify@bfitzexpensify@OlimpiaZurek 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]
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
Activity
melvin-bot commentedon Feb 24, 2025
Triggered auto assignment to @stitesExpensify (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Feb 24, 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.melvin-bot commentedon Feb 24, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Feb 24, 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:
vincdargento commentedon Feb 24, 2025
@bfitzexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
stitesExpensify commentedon Feb 25, 2025
I am suspicious of https://github.com/Expensify/App/pull/56926/files since it is directly related to the debug console
carlosmiceli commentedon Feb 25, 2025
@stitesExpensify what are your thoughts on re: being a blocker (in which case we should revert) vs. removing the blocker label and fixing it? I think it's not a flow that's worth blocking deployment IMO, but not super serious about it :P
16 remaining items
[-]Close account - App opens Debug console page after closing account[/-][+][Due for payment 2025-03-21] Close account - App opens Debug console page after closing account[/+]melvin-bot commentedon Mar 14, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Mar 14, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.12-7 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-03-21. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Mar 14, 2025
@carlosmiceli / @stitesExpensify @bfitzexpensify @OlimpiaZurek 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]
melvin-bot commentedon Mar 21, 2025
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.