Closed hsjoberg closed 1 year ago
I think our template app via 'react--native-macos-init' isn't updated to support the new arch is the short of it. We do support the new app creation stuff (like RCTAppDelegate to get stuff like the concurrentRootEnabled method) not at this moment, you'll have to create the app yourself.
Once this PR is merged, you'll need to blow away the macos
example & re-run npx react-native-macos-init
Description
Hi guys. By reading the commit log and your blog post for react-native-macos 0.71, new architecture appears to be in experimental support. However, I can't find any way to confirm that it's actually enabled.
I've set up latest canary (
npx react-native-macos-init --version 0.0.0-20230601-1643-b45a40a67
) and built the pods usingbundle install && RCT_NEW_ARCH_ENABLED=1 bundle exec pod install
. It looks Fabric-relevant pods are installed.However upon starting a debug build up, I don't see any indication of new arch support, like you would do on Android and iOS:
{"fabric":true,"initialProps":{"concurrentRoot":true},"rootTag":1}
I get conventional non-new arch JSON:
{"rootTag":1,"initialProps":{}}
Furthermore, in AppDelegate.mm I don't see the
concurrentRootEnabled()
function like you would for iOS:Also in the macos Podfile there is no mention of new architectcure or Fabric.
Any suggestions on how I would enable new architecture?
I've also tried running new arch in rn-tester, but I'm instantly getting a crash. I'm not sure if this is expected, I can submit a separate bug report for this if you want me to.
Version
b45a40a
Output of
npx react-native info
Steps to reproduce
npx react-native-macos-init --version 0.0.0-20230601-1643-b45a40a67
andRCT_NEW_ARCH_ENABLED=1 bundle exec pod install
Snack, code example, screenshot, or link to a repository
N/A