[HOLD for payment 2025-01-18] [HOLD for payment 2025-01-17] Workspace - "It's not here" error when I open the invite link from the email as a new member

[IuliiaHerets]

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.82-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check, blank screen opens
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5425296&group_by=cases:section_id&group_id=229065&group_order=asc
Issue reported by: Applause Internal Team
Device used: Windows 10 / Chrome, Apple iPhone 12 Pro / Safari
App Component: Workspace Settings

Action Performed:

1. Navigate to https://staging.new.expensify.com/ in Chrome incognito
2. Log in with a new Gmail account
3. Create a workspace
4. Navigate to Workspace settings - Members
5. Invite a Gmail email to the workspace that doesn't have an Expensify account yet (you should have email access)
6. Open the email client of the member
7. Copy the "new.expensify.com" link address at the bottom of the email
8. Log out as the admin
9. Paste the link to the nav bar and open it

Expected Result:

I should be logged is as the new member.

Actual Result:

"It's not here" error when I open the invite link from the email as a new member.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6708810_1736317913921.bandicam_2025-01-08_07-19-13-885.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @kadiealexander

[melvin-bot]

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

[melvin-bot]

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

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

[IuliiaHerets]

Prod behaviour

bandicam.2025-01-08.09-07-02-229.mp4

[mountiny]

This PR should fix it #54969

[luacmartins]

Fixed in staging

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

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

• [CP Staging] Update validateCode regex to allow base26 codes #54969

If no regressions arise, payment will be issued on 2025-01-17. 🎊

[melvin-bot]

@luacmartins @kadiealexander @luacmartins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot]

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

• [CP Staging] Update validateCode regex to allow base26 codes #54969

If no regressions arise, payment will be issued on 2025-01-18. 🎊

[melvin-bot]

@luacmartins @kadiealexander @luacmartins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]