fix(app): Expo Config Plugin for SDK 53

[hirbod]

Description

As I described here

SDK 53 initialization is failing for the core package @react-native-firebase/app because, as @haddad-yacine correctly pointed out, the AppDelegate.swift has changed and this regexp is failing, thus not adding FirebaseApp.configure().

You can also see

» ios: @react-native-firebase/app: Unable to determine correct Firebase insertion point in AppDelegate.swift. Skipping Firebase addition.

during the prebuild phase.

The patch is pretty easily done by changing the regular expression to

/(?:self\.moduleName\s*=\s*"([^"]*)")|(?:reactNativeFactory\?\.\s*startReactNative)/

I am dropping /g because we only need a single match to locate your insertion point.

The change works as expected and remains backwards compatible.

Fixes #8494 and potentially #8461

Related issues

Release Summary

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • Yes
• My change supports the following platforms;
  • Android
  • iOS
  • Other (macOS, web)
• My change includes tests;
  • e2e tests added or updated in packages/\*\*/e2e
  • jest tests added or updated in packages/\*\*/__tests__
• I have updated TypeScript types that are affected by my change.
• This is a breaking change;
  • Yes
  • No

Test Plan

---

Think react-native-firebase is great? Please consider supporting the project with any of the below:

• 👉 Star this repo on GitHub ⭐️
• 👉 Follow React Native Firebase and Invertase on Twitter

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-native-firebase	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 28, 2025 3:08pm

[CLAassistant]

All committers have signed the CLA.

[mikehardy]

Nice one, thank you for the fix
I rebased to current main (just in case) and did the required lint fix then re-pushed
CI should go green then can merge and will release

[hirbod]

@mikehardy thank you. Just FYI, this PR might need to be updated again, lol: expo/expo#36441

[mikehardy]

@hirbod no good deed goes unpunished right? 😆 at least with regex another matcher can be added easily. That expo PR isn't merged nor released yet so I'm not sure we can take it into account really without risk of making lots of changes here that may never even be needed. However Expo 53 beta is already out, so it stands to reason that merging and releasing this now is useful and follow-ons can be made as needed

[hirbod]

@mikehardy I agree. Adding another matcher won’t be too bad. I’ll keep an eye on it and create a follow-up PR if needed.

[hirbod]

And it happened. New PR incoming