[$1000] Web - Security - Close account - Console error is displayed when closed account

[kbecciv]

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 URL https://staging.new.expensify.com/
2. Login with any account
3. Go to Setting - Security - Close account

Expected Result:

Console error is not displayed when closed account

Actual Result:

Console error is displayed when closed account

Workaround:

Unknown

Platforms:

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

• Web/ Chrome

Version Number: 1.2.59.1

Reproducible in staging?: Yes

Reproducible in production?: Yes

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

Bug5911510_Recording__249.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0127d6eba140b9c56a
• Upwork Job ID: 1618769609192013824
• Last Price Increase: 2023-01-27

[adelekennedy]

@alex-mechler dummy question, can something like this be worked on externally?

[alex-mechler]

This should be able to be worked on externally, this is an error related to sending a message on the socket after it has already been closed generally.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~0127d6eba140b9c56a

[melvin-bot]

Current assignee @adelekennedy is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @aimane-chnaif (External)

[melvin-bot]

Current assignee @alex-mechler is eligible for the External assigner, not assigning anyone new.

[bernhardoj]

I think this has the same root cause with this #14350

[alex-mechler]

Ah good catch @bernhardoj! Going to remove the help wanted label from this for now to confirm that the fix for #14350 also fixes this issue!

[aimane-chnaif]

#14526 is now merged into main and this issue is not reproducible anymore on dev.

[Prince-Mendiratta]

I can confirm that this issue is not related to closing the account flow, root cause was in the logout flow. With the PR merged, this issue will not be reproducible.

[alex-mechler]

Confirmed that its no longer reproducible on dev. Since #14350 has the tracking for payment of @Prince-Mendiratta, and this was reported by Applause, closing this out! Thanks everyone!