-
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
[HOLD for payment 2024-09-10] [$1000] Upgrade to RN 0.75 #37374
Comments
Hey, I would like to work on this issue! |
@MrRefactor I'd strongly recommend you to try https://github.com/infinitered/flame. There's a talk from Jamon it's creator here. I hope it will help streamline the upgrade process for you. |
@roryabraham Sure! I will get gpt-4 and try upgrading with that tool! |
wrote some best practices on RN upgrades earlier today:
|
Update:
|
Update:
|
Update: Created an issue in react-native-quick-sqlite as the same error is visible while building with fresh rn app. In meantime working on a fix for that problem. |
|
Update: Created an issue in |
Update:
|
@MrRefactor The fix for -import com.facebook.react.views.text.CustomLineHeightSpan;
+import com.facebook.react.views.text.internal.span.CustomLineHeightSpan; |
@tomekzaw Thanks Tomek! |
Update:
Working on new issues connected with: Android:
iOS
I will also create issue & pr in |
commented in slack, but I think we should press on with the 0.74 upgrade |
@MrRefactor, let's start doing updates in slack to get more visibility, then just link to the slack updates here in GH. How can we help push this along? What are you doing to parallelize the work here? Can we get more people involved to split up the work? |
@MrRefactor looking forward to seeing an update from you on this project. |
Update on upgrade work: https://expensify.slack.com/archives/C01GTK53T8Q/p1711111014179099 |
@roryabraham, I'm happy to help if a C+ is needed here. |
Upwork job price has been updated to $1000 |
@dylanexpensify This is ready to be paid out to @shubham1206agra for their help on this one and previously with the 0.74 I think $1000 is fair reward for their testing and code review as well as help with follow ups. Let me know if you disagree |
Hi, The issue likely stems from architectural changes in React Native 0.74+ that are incompatible with your current codebase. The need for patches suggests that your existing setup is not fully aligned with the new architecture, which could introduce bugs, performance regressions, or maintainability challenges. Without upgrading, you may face technical debt, increased complexity, and potential conflicts with future React Native updates. One possible short-term fix can be applying specific patches with patch-package to replace modules or dependencies that are not compatible, giving alternative solutions for outdated APIs or components. This enables the project to operate without updating while addressing immediate problems. To achieve a lasting fix, transition completely to React Native 0.74+, restructure code to match the new design, verify third-party libraries work well, and conduct thorough testing to prevent any setbacks or additional issues. This will make the project future-proof, get rid of technical debt, and guarantee long-term stability. Best |
📣 @MuhammadIqbalDev! 📣
|
Payment summary: Contributor+: @shubham1206agra $1000 Please apply/request! |
@dylanexpensify You need to send me an offer through Upwork. |
invited! |
@dylanexpensify Invitation accepted |
offer sent @shubham1206agra! |
@dylanexpensify Offer accepted |
Paid! |
slack context: https://expensify.slack.com/archives/C02NK2DQWUX/p1709024519896479
Problem
There are some new arch problems that should be fixed in RN 0.74+. So far that's the only thing I'm aware of in 0.74+ that we'll need, but it takes a long time to upgrade. It's not necessarily a blocker but unless we upgrade we'll have to use patches.
Solution
Let's get the ball rolling on the RN 0.74 upgrade. If there are issues in the RC we should report them to Meta.
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @dylanexpensifyThe text was updated successfully, but these errors were encountered: