Support new architecture

[andrew-levy]

Blocked by expo/expo#28829

[0xFA11]

should be unblocked by now and I wonder if you have any plans to move towards fabric/jsi anytime soon? 👀

[andrew-levy]

I'm planning on doing this soon. Last time I checked it wasn't working well, but I'll give it another shot soon. Also feel free to give it a shot if you'd like to contribute!

[0xFA11]

I'm actually planning to contribute and was wondering how you were doing. The only thing that holds me back a little bit is the fact that writing Fabric Native Components in Swift is not considered a first class citizen atm. You're expected to expose your Swift code (UIView etc.) over to ObjC/C++ (XXX-Swift.h) and basically do bindings back and forth manually. You also shouldn't rely on bridge backwards-compact layer. So, I'm trying to figure out a comfortable way of writing Swift views and exposing them as Fabric Native Components. If I can get there and have something to offer, I'll come back here :)

[andrew-levy]

@0xFA11 Expo Modules (what this package is using) already supports the new architecture. We would just need to turn on new arch and update anywhere that's relying on didUpdateReactSubviews() since it no longer exists.

[andrew-levy]

@0xFA11 Update on this. I have it somewhat working in the new arch.. will open a PR for at least some of the components once I finish

[wkirby]

@andrew-levy any updates?

[andrew-levy]

@wkirby I ran into issues a few months ago when I tried to make this compatible with the new arch, and I just tried again today and ran into even more issues. I'm going to hold off on this until Expo Modules has sorted out all of their work on supporting swiftui in expo modules.

[mgcrea]

@0xFA11 any update with writing Swift views and using them as native components?

Tried to do that myself today on a new 0.77 project using the now default swift template (with an AppDelegate.swift, no expo) and a third-party library that exposes fabric components. Works fine with objective-c but my library won't compile as soon as I add a swift file (getting missing C++ header errors, like atomic not found), looks like I'm hitting this issue about mixed C++/Swift code...

Was somehow following this blog post but trying to adapt it to 0.77 and the swift template.

Would be great to have a working, up-to-date fabric+swift example out-there!

PS: Beware there is a bug with 0.77 where codegen generates app-level files that must be manually removed if you run codegen yourself... Lost a bit of time on this tonight!