[HOLD 49931] Expensify Card - Empty state screen not visible and issue card button and settings shown

[lanitochka17]

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.56-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team

Issue found when executing PR #49536

Action Performed:

1. Navigate to staging.new.expensify.com
2. Create a workspace and enable Expensify Card
3. Click on Issue card and add a bank account
4. Click on the bank account and wait for it to be verified
5. Go to another workspace and go through the same steps from 1-4

Expected Result:

While the verification is ongoing an empty state screen should be shown on step 4 and on step 5 the issue card button and settings should not be visible

Actual Result:

While the verification is ongoing an empty state screen is not shown on step 4 and on step 5 the issue card button and settings are visible

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6651168_1730383244382.bandicam_2024-10-31_16-52-32-913.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @bfitzexpensify

[melvin-bot]

Triggered auto assignment to @bfitzexpensify (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 @neil-marcellini (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.

[lanitochka17]

We think that this bug might be related to #wave-collect - Release 2

[DylanDylann]

This will be fixed after #51712 is merged

More detail: https://expensify.slack.com/archives/C05LX9D6E07/p1730300375653299?thread_ts=1728966082.429659&cid=C05LX9D6E07

[neil-marcellini]

Thanks for pointing that out @DylanDylann! Sounds like this is a general issue across the whole app due to the way that Network requests are processed. Therefore I'll remove the blocker label and put this issue on HOLD for that one.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[neil-marcellini]

Still holding

• [$250] Chat - Group is created with duplicate user when chat is started quickly on a slow network #49931

[aldo-expensify]

I'm making the backend PR ready for review: https://github.com/Expensify/Auth/pull/13168

[bfitzexpensify]

Cool, we'll be able to circle around to this soon then

[DylanDylann]

@bfitzexpensify This bug has already been fixed

Screen.Recording.2024-12-09.at.14.32.06.mov

[bfitzexpensify]

Nice, let's close this out.