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-02-13] iOS - Wallet - App returns to previous steps when using device gesture on success page #56026
Version Number: 9.0.92-0 Reproducible in staging?: Yes Reproducible in production?: Unable to check If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both If this was caught during regression testing, add the test name, ID and link from TestRail: Exp Email or phone of affected tester (no customers):applausetester+100106kh@applause.expensifail.com Issue reported by: Applause Internal Team Device used: iPhone 15 Pro Max / iOS 18.2 App Component: User Settings
Action Performed:
Precondition:
User has assigned themselves a virtual card.
Go to staging.new.expensify.com
Go to Wallet.
Tap on the card.
Tap Report virtual card fraud.
Tap Deactivate card.
Enter magic code.
On success page, use device gesture to go back (swipe to right on iOS).
👋 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.
@techievivek Yes, it seems you are right - this looks like a regression from my PR you've mentioned above. Please assign me - I'll work on fixing it. Thanks
changed the title [-]iOS - Wallet - App returns to previous steps when using device gesture on success page[/-][+][Due for payment 2025-02-13] iOS - Wallet - App returns to previous steps when using device gesture on success page[/+]on Feb 6, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.94-25 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@alitoshmatov@michaelkwardrop@alitoshmatov 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]
@burczu@mountiny@alitoshmatov@michaelkwardrop this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
[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.
[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.
Activity
melvin-bot commentedon Jan 30, 2025
Triggered auto assignment to @michaelkwardrop (
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 Jan 30, 2025
Triggered auto assignment to @techievivek (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jan 30, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jan 30, 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:
techievivek commentedon Jan 30, 2025
@burczu Seems like this might have originated from your PR here #55278
burczu commentedon Jan 30, 2025
@techievivek Yes, it seems you are right - this looks like a regression from my PR you've mentioned above. Please assign me - I'll work on fixing it. Thanks
16 remaining items
[-]iOS - Wallet - App returns to previous steps when using device gesture on success page[/-][+][Due for payment 2025-02-13] iOS - Wallet - App returns to previous steps when using device gesture on success page[/+]melvin-bot commentedon Feb 6, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Feb 6, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.94-25 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-02-13. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Feb 6, 2025
@alitoshmatov @michaelkwardrop @alitoshmatov 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 Feb 13, 2025
@burczu @mountiny @alitoshmatov @michaelkwardrop this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
melvin-bot commentedon Feb 13, 2025
Payment Summary
Upwork Job
BugZero Checklist (@michaelkwardrop)
alitoshmatov commentedon Feb 13, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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: https://github.com/Expensify/App/pull/55278/files#r1954225671
[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: https://expensify.slack.com/archives/C01GTK53T8Q/p1738211261080969
[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.
No regression is needed
alitoshmatov commentedon Feb 13, 2025
This was a regression so no payment needed
michaelkwardrop commentedon Feb 13, 2025
Closing, no payment needed (regression). Confirming this job was not added to Upwork, so there is no posting to delete.