… module requires

this should ease the transition in general and fail-fast specifically for functions

(cherry picked from commit 2146bf7)
(slightly modified to indicate that it is not required yet, on the release-v23 branch)

…r needed

definitely was needed for react-native-macos 0.74 but no longer needed for
later versions

(cherry picked from commit 0b01c29)

I always attempt `yarn tests:macos:test` before remembering that platform
should be `test-cover`. Adding `test` so it just works for time and there
is no platform difference

(cherry picked from commit ddb1040)

…t hang workaround

(cherry picked from commit 9fb5ab5)

see upstream release notes https://firebase.google.com/support/release-notes/ios#version_1290_-_february_3_2026

(cherry picked from commit ad03c4e)

(cherry picked from commit ff65344)

forgot to do that after converting to modular, so it was returning an
internal error, it works in testing (using rnfbdemo/make-demo.sh) with this
fix deployed

also made sure to deploy in correct project by adding a `firebase use` command
to the functions deploy package.json script

(cherry picked from commit 90e7c1e)

…gEvent (#8879)

(cherry picked from commit 96fad37)

(cherry picked from commit 8a7acf3)

…APTCHA (#8902)

* fix(auth): auto-register encoded app ID URL scheme for phone auth reCAPTCHA

The auth Expo config plugin now derives the Encoded App ID from
GOOGLE_APP_ID (always present in GoogleService-Info.plist) and registers
it as a CFBundleURLScheme, in addition to REVERSED_CLIENT_ID.

This is required for Firebase phone auth reCAPTCHA fallback on iOS
(e.g. Simulator, any device without APNs) even when Google Sign-In is
not enabled. Since April 2023 REVERSED_CLIENT_ID is only present when
Google Sign-In is enabled, so apps using only phone auth had a broken
reCAPTCHA fallback.

Transformation: '1:123456789012:ios:abc123' -> 'app-1-123456789012-ios-abc123'
(cherry picked from commit d2ddbf7)

… then deprecated notification (#8663)

* feat(expo): enhances notification config retrieval

Improves notification configuration by first checking
`expo-notifications` plugin for icon and color.

Falls back to deprecated `config.notification` settings.
Warns about missing notification icon for Android.

* fix lint

* test: make sure both config works

* build(deps): update to Expo 55, handle removed ExpoConfig.notification property

---------

Co-authored-by: Mike Hardy <github@mikehardy.net>
(cherry picked from commit aa63174)

(cherry picked from commit 06426f2)

using the web-targeted firebase-js-sdk implies that we need functioning
implementations of Headers, Request, Response, fetch, and Readable Stream

react-native does not provide those so we polyfill for them whenever we are
using firebase-js-sdk in a native environment and need them

however, Expo can actually use react-native-firebase in a pure web context,
where those things are functioning and need no polyfill - in fact our polyfills
rely on react-native internals and are harmful as they create errors during web
bundling

Expo web uses the metro bundler which allows platform-specific resolution though,
so if we add a no-op polyfills.web file, it is resolved instead of the problematic
polyfills, and everything works

(cherry picked from commit e5685a0)

if we want to publish on branches then we need to checkout from the branch
we run the publish action on, pinning this to main means it will always publish
from main and no branch publish is ever possible

(cherry picked from commit 992f6eb)