You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-10-22] Onboarding - Join workspace intent stuck on workspace list when last name is empty #104038
This is a deploy blocker introduced by #103652, which is on the current staging checklist.
In the new Join my company workspace onboarding flow, users who enter only a first name cannot finish onboarding. Last name is optional on the personal details step, but after a successful join the app treats it as required. The user is sent back toward personal details and stays on the workspace list, even though the join succeeded.
Steps to reproduce
Create a workspace using a private-domain account.
Sign up with another account on the same domain.
Enter a first name and leave the optional last name blank.
Select Join my company workspace.
Click Join now or Ask to join once.
Expected result
Onboarding completes after joining the workspace.
Actual result
The user stays on the workspace list and onboarding does not complete, even though the join succeeded.
Fix
#104016 requires only the first name before completing onboarding and adds a regression test for an empty last name.
Found during internal QA by @carlosmiceli. Screenshots or video to follow.
👋 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:
Identify the pull request that introduced this issue and revert it.
changed the title [-]Onboarding - Join workspace intent stuck on workspace list when last name is empty[/-][+][Due for payment 2026-10-22] Onboarding - Join workspace intent stuck on workspace list when last name is empty[/+]on Oct 15, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.9-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
melvin-bot commentedon Oct 14, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #103652
melvin-bot commentedon Oct 14, 2026
@iwiznia @abzokhattab you have been assigned to this deploy blocker because you reviewed the offending PR: #103652
github-actions commentedon Oct 14, 2026
👋 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:
melvin-bot commentedon Oct 14, 2026
@carlosmiceli you have been assigned to this deploy blocker because you authored the offending PR: #103652
melvin-bot commentedon Oct 14, 2026
💬 A slack conversation has been started in #expensify-open-source
carlosmiceli commentedon Oct 14, 2026
Fixed by CP: #104016 (comment)
m-natarajan commentedon Oct 15, 2026
Issue is not reproducible on Windows 11 / Chrome in v9.5.9-4
bandicam.2026-10-15.15-02-34-014.mp4
[-]Onboarding - Join workspace intent stuck on workspace list when last name is empty[/-][+][Due for payment 2026-10-22] Onboarding - Join workspace intent stuck on workspace list when last name is empty[/+]melvin-bot commentedon Oct 15, 2026
@abzokhattab
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.9-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-10-22. 🎊