[HOLD for payment 2024-12-30] [$250] Android & iOS - Expensify Card - Previous data is not cleared when issuing new card

[IuliiaHerets]

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.69-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp https://expensify.testrail.io/index.php?/tests/view/5285123
Email or phone of affected tester (no customers): applausetester+khcategory18@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

Precondition:

• Expensify Card is set up.

Issue 1:

1. Go to staging.new.expensify.com
2. Go to workspace settings > Members.
3. Tap on any member.
4. Tap New card.
5. Go through card issue flow and remember all the details.
6. After issuing the card, tap New card to issue another card.
7. Go through the card issue flow.
8. Note that the previous data entered in Step 5 is preserved and not reset.

Issue 2:

1. Go to staging.new.expensify.com
2. Go to workspace settings > Expensify Card.
3. Tap Issue card.
4. Go through card issue flow.
5. After issuing the card, tap Issue card to issue another card.
6. Note that app shows the confirmation page from the previous card assignment instead of starting the flow with Step 1.

Expected Result:

When starting another card issue flow after issuing a card, the previous data will be cleared (production behavior).

Actual Result:

When starting another card issue flow after issuing a card, the previous data is preserved.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6681791_1733137032826.Issue_1.mp4

Bug6681791_1733137032831.Issue_2.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021863614110562904926
• Upwork Job ID: 1863614110562904926
• Last Price Increase: 2024-12-02

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @

[melvin-bot]

Triggered auto assignment to @kadiealexander (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 @Julesssss (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.