-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Timeline to official New Architecture support? #4454
Comments
Hey, Thanks a lot for bringing this up and for your interest in the New Architecture. |
We desperately need button to be pressable on a new arch! 😄 I think react-native-paper is my last dependency that lack support, so I hope for the best. 🤞🏻 |
@gedu @lukewalczak Is there any update on this? #4517 is affected by new arch support. |
Hey, I'm pushing forward this PR to move to 0.73. As soon as that's merged, we will try to provide support, but we are discussing internally when exactly that will happen. |
@gedu Have you all decided how you're planning to move forward with new arch support? Myself along with others would be excited to hear since RN 76 and Expo 52 are right around the corner! |
Given that RN 0.76 is out, I'd love to hear more about your future plans for supporting the new architecture. Also, Expo 52 is now in a two week beta phase. |
Having react-native-paper support the latest default architecture including the ability to handle |
Now that Expo 52 is out, it's not possible to install Expo Go 51 on devices that can't directly install APKs (i.e. my phone with a work profile enabled). I'd really like to upgrade to Expo 52 for my project, but this package is holding me back! |
I've read somewhere one of the maintainers left. Is this package still under active maintenance? |
Awesome you managed to find them on Discord @iM-GeeKy. Are you able to press for a rough time estimate on when they will unpause work on this repo? Already 4 months with no changes (including crucial patches) on a repo that's relied upon by so many projects. It is concerning and has caused a rethink on how much my team relies on this library. |
This is pretty concerning -- Paper is a core component of three of my apps. Looks like I may be working at a full rebuild using my own components. |
@iM-GeeKy Is there any patches we could use until these bugs are fixed? |
@VimukthiShohan I'm not a maintainer of the repository, but here is the patch file i'm currently using in my app. It addresses some, but not all of the issues noted above. Hope this helps. patches/react-native-paper+5.12.5.patch
|
@iM-GeeKy Thanks 🎉 |
Can you please estimate how production-ready this patch is in your case? I had to start creating wrapper-components around |
Hey, we just merged this ongoing PR that we had: #4477 |
@gedu Good to hear. When can we expect a new release with these fixes? |
Which is the latest react-native-paper version supported for react-native 0.76.3?
|
Hopefully the new version will be available soon. Thanks for the good work! |
https://reactnative.directory/?search=react-native-paper says new architecture is supported |
Should we expect a new version before end of year? or disable newArc and release? |
Would love an update on this, just to manage expectation and plan accordingly. Especially if the project become maintenance mode. |
Want to note that it's possible to use expo@52 in an old arch and workaround react-native-paper using that. Was not obvious for me.
Is there any announcement or are you talking de-facto? |
@RohovDmytro , no I shouldn't have said that. I have no information. |
New version available now 🎉 |
Oh, yeah! I've just tried it. 50+ screens, 15 minutes of swiping, 0 bugs found yet. Impressive! Thanks! 🤝 |
Is there any sort of timeline towards official New Architecture support (including bridgeless mode and the Fabric renderer)? The React Native team has been pushing hard for packages adjacent to the RN ecosystem to start building in support for the New Architecture, especially with the release of 0.74.x. Apps built with Paper will run in New Architecture projects without any changes, but there are a significant number of small bugs caused by the upgrade (for example: #4445, #4399, #4127). Most of these changes seem to be related to how Paper handles user input. I plan on doing some investigating on my own, but considering the fact that the New Architecture is where the RN ecosystem is moving and that it offers significant performance improvements it would be great to know where the Callstack team stands.
The text was updated successfully, but these errors were encountered: