[HOLD for payment 2024-09-06] [$250] iOS - Wallet - Wallet page freezes after deleting bank account

[IuliiaHerets]

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: v9.0.26-3
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

1. Launch New Expensify app & create a new account
2. Naviagate to Settings >> Wallet >> Add bank account
3. Go through the Plaid flow (Choose Chase bank)
4. Once user navigate back to ND app, select Plaid Saving account option
5. Tap on continue button on Personal bank account added modal & go back to wallet page
6. Tap on 3 dot menu >> delete option >> confirm delete bank account (Note: bank account gets dfeleted)
7. Tap on + add bank account or enable wallet or try clicking the back button

Expected Result:

Wallet page should not freeze on deleting the bank account
Tapping on either add bank account, enable wallet should open plaid flow & clicking back button navigate to settings page

Actual Result:

Wallet page freezes after deleting bank account. Nothing happens on tapping add bank account or enable wallet or the back button

Note: User has force kill app for the options to work in Wallet page

Workaround:

Unknown

Platforms:

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6586929_1724956531886.RPReplay_Final1724955766.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01390fdf36b89f8f00
• Upwork Job ID: 1829450116473018676
• Last Price Increase: 2024-08-30
• Automatic offers:
• eh2077 | Reviewer | 103754230
• allgandalf | Contributor | 103754233

Issue Owner

Current Issue Owner: @CortneyOfstad

[melvin-bot]

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

[melvin-bot]

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

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

[Beamanator]

Looks front-end only b/c it's not reproducible in web & it freezes iOS even when deleting offline

[Beamanator]

This is reproducible in multiple workflows - the point is that you have to open the 3-dot menu, then click "Delete" to open the "Are you sure" modal -> after that, if you cancel or delete or press away, the app "freezes"

I believe the problem is that the first modal hasn't been closed somehow

[daledah]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Wallet page freezes after deleting bank account

What is the root cause of that problem?

When we click the delete option, we don't wait for the current modal to hide first before displaying the next modal

What changes do you think we should make in order to solve the problem?

Make sure that the previous modal is closed before displaying the next modal

Modal.close(() => setIsDeleteModalVisible(true))

What alternative solutions did you explore? (Optional)

In this PR we introduce new prop called shouldCallAfterModalHide. We can wait for this PR to be merged and then use the new props.

[mountiny]

@daledah lets CP the fix now and let that PR go through the normal process. Can you raise a PR please?

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01390fdf36b89f8f00

[melvin-bot]

📣 @daledah You have been assigned to this job!
Please apply to the Upwork job and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Once you apply to this job, your Upwork ID will be stored and you will be automatically hired for future jobs!
Keep in mind: Code of Conduct | Contributing 📖

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @eh2077 (External)

[Beamanator]

PR was CP'd, testing on staging now

[Beamanator]

Fixed on staging - just tested iOS native & web 👍

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.26-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] fix app freeze #48332

If no regressions arise, payment will be issued on 2024-09-06. 🎊

For reference, here are some details about the assignees on this issue:

• @eh2077 requires payment (Needs manual offer from BZ)
• @daledah requires payment (Needs manual offer from BZ)

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@eh2077] The PR that introduced the bug has been identified. Link to the PR:
• [@eh2077] 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:
• [@eh2077] A discussion in #expensify-bugs 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:
• [@eh2077] Determine if we should create a regression test for this bug.
• [@eh2077] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@CortneyOfstad] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[allgandalf]

Can someone assign me here please 🙇

[melvin-bot]

📣 @eh2077 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

[melvin-bot]

📣 @allgandalf 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

[allgandalf]

thanks @Beamanator 🍻

[CortneyOfstad]

Hello! Just getting confirmation on payment as I have not had two PRs tied to the same bug/issue with two different creators. Will follow up and get payment out ASAP once this is confirmed by the team. Thanks for your patience!

[CortneyOfstad]

Thanks for your patience! So it was decided to award the following amounts:

@daledah — $125 for creating a PR that laid the ground work for the solution to be implemented via another PR
@allgandalf — $250 for creating the PR that solved the issue
@eh2077 — $250 for reviewing (to be paid via NewDot)

I am going to send out the manual requests now via Upwork for the two PRs 👍

[CortneyOfstad]

@eh2077 — looks like a contract was created for you in Upwork automatically by mistake, but I have cancelled that in favor of you being paid via NewDot. Thanks!

[CortneyOfstad]

Payment Summary

@allgandalf — paid $250 via Upwork
@daledah — to be paid $125 via Upwork (waiting for you to accept offer)
@eh2077 — to be paid $250 via NewDot

[daledah]

@CortneyOfstad Offer accepted thx

[JmillsExpensify]

$250 approved for @eh2077

[CortneyOfstad]

Updated Payment Summary

@allgandalf — paid $250 via Upwork
@daledah — paid $125 via Upwork
@eh2077 — paid $250 via NewDot