docs(faq): note new architecture status

invertase · Nov 15, 2024 · 2c83533 · 2c83533
1 parent 789d41b
commit 2c83533
Show file tree

Hide file tree

Showing 2 changed files with 16 additions and 0 deletions.
diff --git a/.spellcheck.dict.txt b/.spellcheck.dict.txt
@@ -32,6 +32,7 @@ backoff
 barcode
 Barcode
 barcodes
+bridgeless
 BUGFIX
 CarPlay
 CDN
@@ -82,6 +83,7 @@ github
 globals
 gradle
 Gradle
+headlessJS
 Hesp
 Homebrew
 HTTP
@@ -191,6 +193,7 @@ thenable
 ThreadPoolExecutor
 timezones
 triaging
+TurboModules
 TypeDoc
 UI
 uid

diff --git a/docs/faqs-and-tips.md b/docs/faqs-and-tips.md
@@ -20,6 +20,19 @@ This package wraps `firebase-android-sdk` and `firebase-ios-sdk` into a Javascri
 
 - Some of the modules that are both in the web SDK and native SDK have a great deal more functionality when they can harness native APIs, like messaging (with background delivery that can start your app if not running), like App Check where you can tie the attestation to device-level providers, Storage where you can do background downloads, Performance where you can start measurements from boot, etc.
 
+### Does it work with New Architecture / Fabric / TurboModules ?
+
+Mostly yes. We have been testing with react-native 0.76 in bridgeless mode for
+a while, and people have been running react-native-firebase with new architecture enabled for a while, and the module works.
+
+We are not aware of any problems with the react-native-firebase modules themselves. Please let us know if you see anything.
+
+However, there have been ongoing issues upstream in react-native itself with headlessJS on Android. What does that mean for you?
+
+> If you use FCM / firebase cloud messages to receive background messages in react-native-firebase with `setBackgroundMessageHandler`, you will have problems on new architecture.
+
+Current issue tracker is [https://github.com/facebook/react-native/issues/47570]
+
 ### I need help with [anything regarding <= v5 of React Native Firebase]. Where could I get help with that?
 
 React Native Firebase v5 is now deprecated and unsupported. There's been over a year's grace period provided to migrate to v6, so moving forward maintainers probably won't pay much attention to issues regarding v5. Understandably, upgrading to v6 can take some effort, but staying on v5 probably isn't a great choice for the long-term health of your project.