Home - After logging in via public room and opening announcement link, app returns to login

[mitarachim]

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.3.11-17
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #80965
Email or phone of affected tester (no customers): sidnjosdnjdosijsojns@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Other

Action Performed:

1. Go to staging.new.expensify.com
2. Log out.
3. Open public room link - https://staging.new.expensify.com/r/6481614786553111
4. Go to Home > Inbox > Home.
5. Click on 3rd announcement link.
6. Create a new account and complete the onboarding with Something else intent.
7. Click on the same announcement link.

Expected Result:

In Step 5, as anonymous user, announcement link should open the link directly without login.
In Step 7, announcement link will open.

Actual Result:

In Step 5, as anonymous user, login is required to open annoucement link.
In Step 7, after opening annoucement link, user is dropped to login page.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7062455_1769829270556.07.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @WojtekBoman

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #80965

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[melvin-bot]

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