Skip to content

Commit dd979a8

Browse files
committed
docs(faq): note new architecture status
1 parent 789d41b commit dd979a8

File tree

2 files changed

+17
-1
lines changed

2 files changed

+17
-1
lines changed

.spellcheck.dict.txt

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,7 @@ backoff
3232
barcode
3333
Barcode
3434
barcodes
35+
bridgeless
3536
BUGFIX
3637
CarPlay
3738
CDN
@@ -82,6 +83,7 @@ github
8283
globals
8384
gradle
8485
Gradle
86+
headlessJS
8587
Hesp
8688
Homebrew
8789
HTTP
@@ -191,6 +193,7 @@ thenable
191193
ThreadPoolExecutor
192194
timezones
193195
triaging
196+
TurboModules
194197
TypeDoc
195198
UI
196199
uid

docs/faqs-and-tips.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,19 @@ This package wraps `firebase-android-sdk` and `firebase-ios-sdk` into a Javascri
2020

2121
- 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.
2222

23+
### Does it work with New Architecture / Fabric / TurboModules ?
24+
25+
Mostly yes. We have been testing with react-native 0.76 in bridgeless mode for
26+
a while, and people have been running react-native-firebase with new architecture enabled for a while, and the module works.
27+
28+
We are not aware of any problems with the react-native-firebase modules themselves. Please let us know if you see anything.
29+
30+
However, there have been ongoing issues upstream in react-native itself with headlessJS on Android. What does that mean for you?
31+
32+
> If you use FCM / firebase cloud messages to receive background messages in react-native-firebase with `setBackgroundMessageHandler`, you will have problems on new architecture.
33+
34+
Current issue tracker is [https://github.com/facebook/react-native/issues/47570](https://github.com/facebook/react-native/issues/47570)
35+
2336
### I need help with [anything regarding <= v5 of React Native Firebase]. Where could I get help with that?
2437

2538
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.
@@ -28,7 +41,7 @@ The longer you stay on v5, the more your project will be out of sync with the of
2841

2942
We highly recommend taking the necessary pains to update to v6.
3043

31-
### My CI build hangs at the "Running script '[CP-User] [RNFB] Core Configuration'" step.
44+
### My CI build hangs at the "Running script '[CP-User] [RNFB] Core Configuration'" step
3245

3346
This may be fixed by creating a `firebase.json` file at the root of your project if it's not there already. If you don't want to change any of the default React Native Firebase configurations, you can leave it empty in the following way:
3447

0 commit comments

Comments
 (0)