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
Selecting the option "Submit expenses to my employer" during onboarding opens Settings > Categories and #admins RHP without welcome message #94324
Version Number: Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: Slack conversation (hyperlinked to channel name):
The user should land in "Home" for the Submit expenses flow (much like other intents) and see the appropriate onboarding/welcome messaging or the tasks list.
The flow should not navigate unexpectedly to Settings > Categories with the #admins room open in the RHP.
Actual Result:
After selecting “Submit expenses to my employer”, the app navigates to Settings > Categories and opens the #admins room in the RHP. No welcome message is shown.
Workaround:
The user can continue using the app by navigating manually, but the onboarding landing experience is confusing and appears incomplete.
Platforms:
Select the officially supported platforms where the issue was reproduced:
changed the title [-]Submit expenses onboarding opens Settings > Categories and #admins RHP without welcome message[/-][+]Selecting the option "Submit expenses to my employer" during onboarding opens Settings > Categories and #admins RHP without welcome message[/+]on Jun 23, 2026
Activity
[-]Submit expenses onboarding opens Settings > Categories and #admins RHP without welcome message[/-][+]Selecting the option "Submit expenses to my employer" during onboarding opens Settings > Categories and #admins RHP without welcome message[/+]inimaga commentedon Jun 23, 2026
This seems like the desired behaviour, so closing this out for now as not planned.