-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$2000] App fails on devices using recent node/npm with JavaScript error - reported by David Frenkiel #8888
Comments
Triggered auto assignment to @marcaaron ( |
Not running an M1 mac so can't properly test this. |
Triggered auto assignment to @kevinksullivan ( |
This issue affects not only m1 macbooks. |
@kevinksullivan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel ( |
Kindly bump this down to |
@parasharrajat sorry I didn't see the issue you're referring to. Can you let me know if you're able to find it if we think it'll include valuable context? |
Sorry @kevinksullivan, I am not sure which issue are you referring to. |
Ah, wrong issue. Disregard. |
Still waiting on proposals, updating the price. |
Price doubled. |
I think we are actually working on this one internally and might be able to close this |
@frenkield can you apply for the job so I can pay the reporting bonus? i'm not having any luck with Upwork search. |
Thanks, @kevinksullivan. I just applied. |
Hired! Mind accepting and then I can pay this out @frenkield ? |
All set, @kevinksullivan. |
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:
Expected Result:
App runs without invalid hook call JavaScript error.
Actual Result:
Browser window opens and remains blank, and there’s an invalid hook call... error in the JavaScript console.
There do appear to be invalid hook calls in react-native-safe-area-context in SafeAreaContext.tsx.
Workaround:
Using an old node/npm version (e.g. 14.9.0/6.14.8) resolves the issue.
Platform:
Where is this issue occurring?
Version Number: 1.1.56-0
Reproducible in staging?: need repro
Reproducible in production?: need repro
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @ David Frenkiel
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1650494818552169?thread_ts=1650471398.505469&cid=C01GTK53T8Q
Job Post: https://www.upwork.com/jobs/~01570a3972089306b9
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: