Expensify Card - Clicking on the bank account on a new workspace does nothing at first

[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. Connect bank account
4. Create another workspace
5. Enable Expensify Cards
6. Go to expensify cards and click on issue new card
7. Click on the bank account added on the previous workspace
8. Click again

Expected Result:

App should navigate to the next page on the first click

Actual Result:

App does nothing when clicking on the bank account but another page appears after waiting for a while

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

Bug6651198_1730385581085.bandicam_2024-10-31_17-30-16-556.mp4

View all open jobs on GitHub

[melvin-bot]

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

[Julesssss]

Thanks @DylanDylann. So I see that Aldo is needed for the backend change and is OOO for 2 weeks.

For the following reasons I'm not going to hold the deploy on this:

• Backend deploys will block us for DAYS, even after it is fixed
• This feature does work, it's just confusing as there is no feedback

[melvin-bot]

@Julesssss 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[Julesssss]

I bumped the PR, which seems to be stuck in review

[melvin-bot]

@Julesssss Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[Julesssss]

Still awaiting the fix for this PR: #50423

[melvin-bot]

@Julesssss Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[Julesssss]

Held as we await fix mentioned here

[melvin-bot]

@Julesssss Huh... This is 4 days overdue. Who can take care of this?

[Julesssss]

Same as above

[Julesssss]

Here's the latest update from the held issue.

[melvin-bot]

@Julesssss Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[Julesssss]

Held on another fix

[Julesssss]

Requesting retest as the linked bug has been resolved.

[Julesssss]

I accidentally added overdue, removing again