I wrote the original integration doc used by reactnative.dev so yeah. However! When we turned on the integrated toggle in react-native-google-mobile-ads repo we had one contributor that didn't have ccache installed in their machine and it didn't handle that, manual integration did...
Big tip of the hat to the react-native releases crew.
I track their releases with rigorous build testing to ensure react-native-firebase builds cleanly. Zero issues with the upcoming 0.77 release through entire rc cycle.
react-native 0.77.0 full release coming soon and I'm looking forward to it!
Guess I'm on the late late late show but I'd never seen this in particular or heard you play in general. Yeah so... mind blown! Wife and I just watched, mouths open. Fantastic, chapeau
100%! Nothing beats a good reproducer. Will say this was tag team the whole way as you all made that cloneable reproducer template which really simplified creation of the thing. Gives me ideas for the repos I manage as we do not typically get great reproducers...
Current #reactnative new architecture status for #reactnativefirebase and #notifee --> no known problems in current versions of everything. Upgrade. Test things out. Holler at me if you find something... Cheers
as far as I know, background FCM will not work on android because of the headlessJS issue. 0.76.2 still has issues and there's not even a PR yet so obviously no pick to 0.76.3 yet. So if you rely on background messages on android you'll have to disable new architecture. No other known issues tho
You'd think I would have realized documenting the current status would be useful. I should do that 😆🤦
A bit of a bumpy ride so far. appears that most things work so it doesn't hurt to try. As react-native-firebase / notifee maintainer I'm currently struggling with headlessJS not working and foreground-services issues, but otherwise all is working