Timeline to official New Architecture support?

[micahlt]

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.

[gedu]

Hey, Thanks a lot for bringing this up and for your interest in the New Architecture.
Right now, we're in the process of upgrading react-native-paper to version 0.73. Once that's done, our next step is to work on full compatibility with the New Architecture.
We know it's important and are on it. Appreciate your patience and support!

[RohovDmytro]

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. 🤞🏻

[iM-GeeKy]

@gedu @lukewalczak Is there any update on this? #4517 is affected by new arch support.

[gedu]

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.

[iM-GeeKy]

@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!

[hakonk]

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.

[iM-GeeKy]

@gedu For convenience, here is a running list of open issues potentially blocking teams from migrating to the new arch. Any update for new arch support would be greatly appreciated since the library hasn't been updated in 4 months and is a critical part to many projects.

• [Android-Only] Snackbar visibility issue with RN New Architecture #4445
• Chip onPress doesn't work on android device #4399
• TextInput label invisible before focusing on new architecture #4127
• Modal will appear once more when its mask is clicked. #4140
• Label is hidden when a multiline TextInput is focused on iOS #4482
• ProgressBar crashes app in new arch on android #4544
• New Architecture and React Native 75/76 #4545
• Cannot remove child at index X from parent ViewGroup X, only Xchildren in parent. Warning: childCount may be incorrect! #4546
• TextInput label is breaking in new architecture #4552
• [newarch][android] portal now flickers when onDismiss #4555
• Changing Button Mode doesn't work dynamically (Expo 52) #4559
• New arch disabled button theme color #4520
• Issues in jest tests with expo 52, react 0.76 and new architecture #4561
• Button background color does not update when switching themes on Android #4570

[RohovDmytro]

Having react-native-paper support the latest default architecture including the ability to handle onPress, which is quite crucial, would be amazing.

[shoffing]

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!

[RohovDmytro]

I've read somewhere one of the maintainers left. Is this package still under active maintenance?

[iM-GeeKy]

Just for everyone's visibility. I reached out on Discord and received the following response.