[Due for payment 2026-01-29] iOS - App crashes after inviting non-existing member to the room

[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.5-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #79299
Email or phone of affected tester (no customers): jsat+555Nnew@applausemail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: iPhone 13 mini/18.6.2
App Component: Other

Action Performed:

1. Launch Expensify App
2. Log in with a new account
3. Select Manage my team then continue with the onboarding flow
4. Click FAB >> Start Chat >> Room >> Enter Room name >> Create Room
5. After user is directed to the created Room >> Click header >> Member >> Invite non-existing member to the room

Expected Result:

Non-existing member is invited to the room and the user is able to perform the remaining steps

Actual Result:

App crashes after inviting a non-existing member to the room and the user is not able to perform the remaining steps

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7054365_1769003863398!system.txt

Bug7054365_1768949624502.BUG-iOS.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @JmillsExpensify

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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