[$250] BUG: DEV - Console error on web app load react-dom.development.js?.. - reported by @aneequeahmad

[mvtglobally]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. Launch web app
2. See the error in console.

Expected Result:

No Errors should display

Actual Result:

Console error on web app load react-dom.development.js?61bb:86 Warning: ReactDOM.render is no longer supported in React 18. Use createRoot instead. Until you switch to the new API, your app will behave as if it's running React 17.

Workaround:

unknown

Platform:

Where is this issue occurring?

• Web

Version Number: 1.2.12-3
Reproducible in staging?: N
Reproducible in production?: N
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

bug-dev-react18.mov

Expensify/Expensify Issue URL:
Issue reported by: @aneequeahmad
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1661251204472079

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @sakluger (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @srikarparsi (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[parasharrajat]

There is an internal issue #11680 which is going to fix it. Thus this is kind of duplicate. And we have been discussing this #8503 for a long time.

[sakluger]

Thanks @parasharrajat - if this is a duplicate, do you recommend closing this one?

[michaelhaxhiu]

@parasharrajat do you think we ought to pay a reporting bonus for this when the internal issue is resolved? cc @roryabraham since you are assigned to the internal issues.

IMO this doesn't get paid and closed until we decide if (1) it's a tue duplicate or not and (2) the problem is actually fixed.

[parasharrajat]

So this was reported on Aug 23 and we created an internal issue on #8503 (comment).

Seems like eligible for reporting bonus. I suggest closing this one and updating #11680 if eligible for reporting bonus.

[roryabraham]

Fair's fair – @aneequeahmad beat me to reporting this so I agree with @parasharrajat's last message.

[sakluger]

Cool, closing in favor of #11680. I left a comment on that issue that @aneequeahmad should be paid the reporting bonus once it's completed.