[$250] DEV: Investigate the console errors that show up after signing in

[youssef-lr]

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:
Reproducible in staging?:
Reproducible in production?:
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
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:

Action Performed:

1. Sign in to NewDot locally

Expected Result:

Ideally, no error should be shown in the console.

Actual Result:

Many console errors show up and they are distracting, it's hard to know which one of them is causing a UI issue.

As of now here are the errors I'm seeing:

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01b447136e274124b6
• Upwork Job ID: 1813619813398356556
• Last Price Increase: 2024-07-31
• Automatic offers:
• hoangzinh | Reviewer | 103403426

Issue Owner

Current Issue Owner: @hoangzinh

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01b447136e274124b6

[melvin-bot]

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

[melvin-bot]

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

[mosesbabu]

Please re-state the problem that we are trying to solve in this issue.
Investigate the console errors that show up after signing in

What is the root cause of that problem?
1.the View components may have plain text is directly inside them will check Wrap all text with Text components.
2.some libraries are using deprecated methods like findDOMNode will check and update them
What changes do you think we should make in order to solve the problem?

1. will check Wrap all text with Text components.
2. will check libraries using depreciated methods such as findDOMNode and update them

[hoangzinh]

Hi @mosesbabu can you format your proposal same as PROPOSAL_TEMPLATE here? Besides that, the root cause needs to be more details and clearly point out which is causing the issue. Thank you.

[mosesbabu]

ok noted doing so right now. was asking if the issue is not yet assigned as well thank you

[hoangzinh]

yep, it is still open for proposals

[mosesbabu]

Proposal

i recreated the error locally there are more errors as well on the console apart from these can check them as well

Please re-state the problem that we are trying to solve in this issue.

Investigate the console errors that show up after signing in

What is the root cause of that problem?

The RCA was not how react handled the routes but this is fixed

• Fixed

• In progress
  
  caused by findDomNode being depreciated in StrictMode

What changes do you think we should make in order to solve the problem?

Verify that objects from which are reading properties are not undefined.
Add null or undefined checks before accessing properties

Ensure findDOMNode is not used directly.
Update any libraries that rely on findDOMNode to their latest versions

What alternative solutions did you explore? (Optional)

there are so many other errors i can clear them all if hired