[HOLD for payment 2023-09-04] Task -App becomes unresponsive when Assign Task to user that doesn't have a NewDot account yet

[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. Navigate to staging.new.expensify.com
2. Go to FAB > Assign Task > Enter title and description and navigate to next page
3. Click on Assignee
4. Enter a email that doesn't have a NewDot account yet
5. Create the task

Expected Result:

Assignee should be added immediately and no errors should appears

Actual Result:

App becomes unresponsive when Assign Task to user that doesn't have a NewDot account yet
Page Unresponsive
You can wait for it to become responsive or exit the page

Workaround:

Unknown

Platforms:

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

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

Version Number: 1.3.56-0

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

Bug6173285_Recording__776.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 @marcochavezf (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[marcochavezf]

Seems we're entering an infinite loop after assigning the task

[marcochavezf]

We're calling multiple times componentDidUpdate in ReportScreen.js

Screen.Recording.2023-08-22.at.14.20.50.mov

I will need to step out for 1.5 hours approx, I will continue when I come back

[marcochavezf]

The OpenReport and CreateTask are failing:

[marcaaron]

Doing the repro steps for this is causing a crazy infinite loop that crashes the browser for me. Happens on both production API and staging API.

It's pretty bad. The app becomes unusable.

[marcaaron]

These three PRs are related to tasks:

#24506
#24412
#24566

Not sure if any of them are related to this regression. @Julesssss @arosiclair @luacmartins might have a better idea.