-
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-04-25] [Tracking] [Performance] Enable the new Fabric architecture #8503
Comments
Triggered auto assignment to @stitesExpensify ( |
This can definitely be external. I went ahead and flagged it as a potential issue for the Margelo team to work on: https://expensify.slack.com/archives/C035J5C9FAP/p1649217447621559 |
Awesome, Margelo would love to work on this! We noticed that you use a lot of third party React Native libraries, so it'll be a bit difficult to get those migrated as well. Especially problematic is Reanimated, but the SWM team is working on bringing that to Fabric. Let's coordinate internally which issue we want to prioritize :) |
Making this a weekly while we prioritize |
Moving to monthly |
@mrousavy just for clarity on this issue, where is it currently prioritized? |
I believe currently we are not working on this issue, maybe let's discuss this in the Slack channel? We are currently working a lot with Coinbase and have very limited availability, but we expect to have some in two weeks! |
I've stumbled on this ticket thanks to experimenting with Fabric and the new RN Architecture. I think we can
I'm posting a comment to keep in touch |
Thanks for volunteering @kidroca! There is still a lot of internal conversation happening around this, so I'll post an update when I have one 😄 |
Relevant discussion: https://expensify.slack.com/archives/C035J5C9FAP/p1655407547697249 |
No updateyet |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.62-17 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-04-25. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@ishpaul777 , can you let me know when I should issue payment here? Lotta PRs keep auto-posting and pushing back the payment date. Thx |
@roryabraham Can you please clarify payment date here, i think we blocked deploy for android yesterday until #40048 is fixed, does that effect the payment date |
I don't think it should, because it's an inconsistently reproducible bug in the RN Fabric renderer C++ code. I think we should pay this out on 2024-04-25, one week after the main Fabric PR went to prod (yesterday). |
Groovy, I'll pay on 4/25, thx |
Issue is ready for payment but no BZ is assigned. @joekaufmanexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
Payment Summary
BugZero Checklist (@joekaufmanexpensify)
|
@mallenexpensify I see based on above comments you have been tracking payments/BZ for this one, so assigned to you. LMK if there is anything I can help with though! |
@ishpaul777 can you please accept the job and reply here once you have? |
Offer accepted😄 Thanks |
Contributor+: @ishpaul777 paid $2000 via Upwork. Thanks! Are there any new regression tests we want for this? cc @roryabraham |
No additional regression tests needed for this. Thanks for the great work everyone. This was a big one. Closing this out! |
GitHub Project: https://github.com/orgs/Expensify/projects/35
Main New Arch PR: #13767
Context
New render engine: https://reactnative.dev/architecture/fabric-renderer
Summary of findings
Requirements
Migrate off setNativeProps
Migrate off findNodeHandle
Bidirectional scrolling
Dependency upgrades
FastImageno longer in useKnown bugs
Expensify/Expensify Issue URL:
Issue reported by: @roryabraham
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1648743262264529
The text was updated successfully, but these errors were encountered: