Skip to content

[Due for payment 2025-02-13] iOS - Wallet - App returns to previous steps when using device gesture on success page #56026

Closed

Description

@mitarachim

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.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.
  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

Issue OwnerCurrent Issue Owner: @michaelkwardrop

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Jan 30, 2025
  2. melvin-bot commented on Jan 30, 2025

    @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.

  3. melvin-bot commented on Jan 30, 2025

    @melvin-bot

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

  4. melvin-bot commented on Jan 30, 2025

    @melvin-bot

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

  5. github-actions commented on Jan 30, 2025

    @github-actions
    Contributor

    👋 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.
  6. techievivek commented on Jan 30, 2025

    @techievivek
    Contributor

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

  7. burczu commented on Jan 30, 2025

    @burczu
    Contributor

    @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

  8. self-assigned this
    on Jan 30, 2025
  9. 16 remaining items

  10. 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
  11. melvin-bot commented on Feb 6, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Feb 6, 2025

    @melvin-bot

    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:

    • @burczu does not require payment (Contractor)
    • @alitoshmatov requires payment through NewDot Manual Requests
  13. melvin-bot commented on Feb 6, 2025

    @melvin-bot

    @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]

  14. melvin-bot commented on Feb 13, 2025

    @melvin-bot

    @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!

  15. melvin-bot commented on Feb 13, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Contributor: @burczu is from an agency-contributor and not due payment
    • Reviewer: @alitoshmatov owed $0 via NewDot (regression)

    BugZero Checklist (@michaelkwardrop)

    • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  16. alitoshmatov commented on Feb 13, 2025

    @alitoshmatov
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:

    No regression is needed

  17. alitoshmatov commented on Feb 13, 2025

    @alitoshmatov
    Contributor

    This was a regression so no payment needed

  18. michaelkwardrop commented on Feb 13, 2025

    @michaelkwardrop
    Contributor

    Closing, no payment needed (regression). Confirming this job was not added to Upwork, so there is no posting to delete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions