Login with existing account–After login via link user redirect on "Hmm... it is not here" page

[lanitochka17]

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: 1.3.89-6

Reproducible in staging?: Yes

Reproducible in production?: No

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

Action Performed:

1. Open https://staging.new.expensify.com/.
2. Log out
3. Navigate to this link - https://staging.new.expensify.com/concierge
4. Log in with ponikarchuks+2@gmail.com.

Expected Result:

Navigated to the concierge chat after login

Actual Result:

"Hmm... it is not here" page opens when navigate via deeplink https://staging.new.expensify.com/concierge
and log in with ponikarchuks+2@gmail.com
account
"Hmm... it is not here"

Workaround:

Unknown

Platforms:

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

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

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

Windows: Chrome

Bug6247930_1698090387757.Error_message_when_navigate_to_concierge_chat.mp4

logs2.txt

MacOS: Desktop

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @zanyrenney (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[OSBotify]

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

[melvin-bot]

Triggered auto assignment to @tylerkaraszewski (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[tylerkaraszewski]

I could not reproduce this problem with my account:

[tylerkaraszewski]

@zanyrenney - do you want to see if this happens for you?

[marcaaron]

I can't repro either. Let's demote.

[zanyrenney]

I don't know why this was assigned to me at 22.45 my time but i was not online 😓 @tylerkaraszewski

[zanyrenney]

I have tried now and I also can't reproduce, should we make this daily instead?

[tylerkaraszewski]

I'm gonna close it since nobody can make it happen.