iOS - Wallet - App returns to previous steps when using device gesture on success page

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

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): [email protected]
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.

1. Go to staging.new.expensify.com
2. Go to Wallet.
3. Tap on the card.
4. Tap Report virtual card fraud.
5. Tap Deactivate card.
6. Enter magic code.
7. On success page, use device gesture to go back (swipe to right on iOS).

Expected Result:

App will return to Wallet page.

Actual Result:

App returns to previous deactivating card steps.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6728130_1738205821566.ScreenRecording_01-30-2025_10-53-09_1.mp4

View all open jobs on GitHub

[melvin-bot]

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]

Triggered auto assignment to @techievivek (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[techievivek]

@burczu Seems like this might have originated from your PR here #55278

[burczu]

@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

[mountiny]

Happy to take over as I have worked with @burczu on the PR

[burczu]

@mountiny This one is quite tricky actually - I was able to fix it partially, by calling Navigate.closeAndNavigate to open the success page. It closes the Report Virtual Card page before showing the Success page, and this is what we need. Then, when the user slides right using gestures, it lands on the Card Details Page (which is correct). Unfortunately this page is not updated with the new cardID so it shows $0.00 etc. (when user taps Got it! or the Go Back button it is actually navigated to the new Card Details Page with correct cardID).

I think we may need to handle this gesture programmatically using react-native-gesture-handle here. What do you think? Any other ideas?

[burczu]

@mountiny Ok, I have another idea, but it may look kinda' hack'ish - we can remove the Card details page from the stack while we redirecting to the Success page: this way when user uses gestures to close the page, it will land on the Settings -> Wallet page... If they tap on Got it button or on the Go back button it will land on correct Card details page as before. WDYT?

[mountiny]

Demoting as the users are not blocked by this action and its mainly about specific ux flow, i dont want to make rushed decisions

[mountiny]

Discussing in the slack thread

[burczu]

The PR is ready for review.