[HOLD for payment 2023-07-21] [HOLD for payment 2023-07-20] New Task - Crash when choosing Assignee as phone number

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Go to any chat
2. Click on + icon
3. Select Assign task option
4. Enter the title and description of the data > Next
5. Select Assignee as number phone
6. Enter title and click on next button
7. Click on Confirm task button

Expected Result:

App doesn't crash

Actual Result:

Crash when choosing Assignee as phone number (Web)
In IOS appears Hmm... its not here
You don't have access to this chat

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.39.5

Reproducible in staging?: Yes

Reproducible in production?: No

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug6124129_Recording__2800.mp4

Bug6124129_ios_1107_crash.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[OSBotify]

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

[melvin-bot]

Triggered auto assignment to @roryabraham (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[francoisl]

I can't reproduce the issue on staging nor dev. I wonder if it's a backend issue with the account you were using specifically. Any chance you can share the email address of the account you were using so I can check backend logs please?

[francoisl]

Internal logs of a crash for this here.

NewExpensify crash caught by error boundary - Cannot read property 'avatar' of undefined ~~ errorInfo: '{"componentStack":" in TaskView in WithCurrentUserPersonalDetails(TaskView) in Unknown in withOnyx(Component) in Unknown in Unknown in Unknown in ReportActionItem in withOnyx(Component) in Unknown in Unknown in Unknown in Unknown in Unknown

The stacktrace is pointing to reading a .avatar in TaskView... @jasperhuangg any chance this could be on this line?

[francoisl]

I was able to reproduce the crash, the key is that you have to create a task with a phone number you've never interacted with before. I think the issue is the line I pointed to before, working on a fix.