Thread - App signs out user after leaving thread

[izarutskaya]

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: 9.0.11-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: https://expensify.testrail.io/index.php?/tests/view/4753349
Email or phone of affected tester (no customers): bezawitgebremichael+kk@gmail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

1. Navigate to staging.new.expensify.com
2. Sign in with a new account (Must be a new account)
3. Open a chat
4. Send a message
5. Click on reply in thread
6. Send a message
7. Click on header
8. Click on leave

Expected Result:

App stays signed in

Actual Result:

App signs out user if a user with a new account clicks on leave thread

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

Bug6550233_1721709922103.bandicam_2024-07-23_07-36-01-635.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[izarutskaya]

We think this issue might be related to the #vip-vsb

[izarutskaya]

Production

Recording.2638.mp4

[puneetlath]

I don't think this is a blocker, though we should decide what we want the behavior to be when an unvalidated user takes this action.

[melvin-bot]

@puneetlath, @anmurali Whoops! This issue is 2 days overdue. Let's get this updated quick!

[puneetlath]

I'm going to go ahead and close this. We're working on updating the unvalidated user flow and this is pretty edge-case, so I don't think it's worth the time right now.