-
Notifications
You must be signed in to change notification settings - Fork 7
Open
Description
Starting with Expo SDK 55 (React Native 0.83), the
New Architecture is always enabled and cannot be
disabled. This means libraries using the old
bridge-based API need to migrate to Turbo Modules
and Fabric to remain compatible.
Are there plans to add New Architecture support to
courier-react-native?
Current Issues
The library currently uses legacy bridge patterns
that are incompatible with the mandatory New
Architecture in RN 0.83+:
- SimpleViewManager — Used in
CourierPreferencesViewManager.kt and other view
managers. Fabric requires the new ViewManager
codegen spec approach. - ReactNativeModule / bridge-based native modules
— Turbo Modules are required for full New
Architecture support. - currentActivity casting — Already fragile in RN
0.81 (we maintain a patch for null safety), likely
to break further in bridgeless mode.
While React Native provides an interop layer for
backward compatibility, it is not guaranteed to
work for all cases and is intended as a temporary
bridge, not a long-term solution.
Environment
- @trycourier/courier-react-native: 5.6.17
(latest) - Current project: Expo SDK 54 / RN 0.81, planning
upgrade to SDK 55 / RN 0.83 - Platform: iOS + Android
Questions
- Is New Architecture / Turbo Module support on
the roadmap? - If so, is there an estimated timeline?
- Has the library been tested against RN 0.82+ or
0.83 with the interop layer?
References
- Expo SDK 55 announcement — New Architecture
always enabled - React Native New Architecture guide
- Library support for New Architecture
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels