[HOLD for payment 2024-08-19] Login - Concierge chat is not opened when signing in

[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.18-0
Reproducible in staging?: Y
Reproducible in production?: N
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

Action Performed:

1. Navigate to https://staging.new.expensify.com/
2. Reload the page making sure that you are on staging.new.expensify.com
3. Sign in with a new applause.expensifail account

Expected Result:

Concierge chat opens

Actual Result:

Black page is displayed

Workaround:

Unknown

Platforms:

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

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6565060_1723071601689.Screen_Recording_2024-08-08_at_1.51.13_at_night.mov

View all open jobs on GitHub

[melvin-bot]

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

[lanitochka17]

We think that this bug might be related to #vip-vsp

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

[dangrous]

aw man, this comes from one I reviewed. #46623 / #44600

Not a backend blocker though.

We might want to revert, unless there's an obvious fix.

[HezekielT]

@dangrous I think it's better to completely revert the original PR as I was not able to fix this issue without reintroducing the original issue.

[HezekielT]

@dangrous Here is the link to the PR #47099

[dangrous]

Got it, merging and will request a CP to staging

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

[dangrous]

The revert is confirmed to have fixed this, as it is no longer reproducible on staging after the CP! Closing.

[melvin-bot]

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

• Revert "Fix - no abracadabra page shown" #47099

If no regressions arise, payment will be issued on 2024-08-19. 🎊