CLA assistant check
All committers have signed the CLA.

Hello 👋, this PR has been opened for more than 2 months with no activity on it.

If you think this is a mistake please comment and ping a maintainer to get this merged ASAP! Thanks for contributing!

You have 15 days until this gets closed automatically

Is anyone going to look into this?

i think they're waiting for 0.72 to be released to merge

does firebase/messaging needs to be migrated to new arch too ? @andresribeiro

Is there any list of remaining tasks in order for this to work?

We use RNFB a lot and would like to get some benefits from new architecture as well, we also prefer to keep RNFB if possible instead of switching to something else, so we are happy to contribute based on an estimation of efforts required.

Hello 👋, this PR has been opened for more than 2 months with no activity on it.

If you think this is a mistake please comment and ping a maintainer to get this merged ASAP! Thanks for contributing!

You have 15 days until this gets closed automatically

This is on my radar and it's getting closer to possible with both mixed new/old modules supported and use_frameworks better supported - apologies for the delay / lack of communication. react-native-firebase is actively supported and that necessarily implies that new architecture is very interesting to merge!

Hello 👋, this PR has been opened for more than 2 months with no activity on it.

If you think this is a mistake please comment and ping a maintainer to get this merged ASAP! Thanks for contributing!

You have 15 days until this gets closed automatically

Hello, is there any news on unifying support for the new architecture?

In react-native 0.72+ there are reports that running New Architecture in your app works, as long as you are in the transition / bridged mode - bridgeless mode is not reported to work. I have not tested it myself.

We are not currently working on actually converting to New Architecture yet, but as it is the future, we'll have to at some point

Thanks for the answer! We’ll have to try, but of course it would be very cool if react-native-firebase received full support faster; this is one of the few libraries (and at the same time the most important) that is slowing down our transition to a new architecture =(

If this module works (as reported success indicates it does) using the interop layer they added in 0.72 I believe that unblocks your app and everyone though, even without this module going through the internal rebuild?

That's my understanding, I'm hoping that's correct - use_frameworks support was totally blocking us but now that it's not we would be the blocker if we're not working (at least with interop layer) and I'm hoping we are not the blocker any longer

Hi @mikehardy, do you think this can be reopend and merged?

I can reopen it - are you willing to test it @GideonAgboba ? Invertase has native new architecture support on the radar but I must emphasize: there is no problem running react-native-firebase currently with new architecture enabled in bridgeless mode. There is nothing currently stopping you from using it. I believe the large-scale roadmap here is to deprecate the old firebase-js-sdk API (currently in process) so that the modular API is the only one in use, then migrate to typescript, and then new architecture support. With Vertex AI support in there somewhere as well. Each of these is large jobs though and in open source work ETAs should never be promised, as there are not really paying customers right?