fix(app, expo): update iOS AppDelegate for SDK 53 support

[LeonDvlpmnt]

Description

In #8324 support was added for Swift templates. However this was done based on the AppDelegate.swift of react-native and not on the AppDelegate.swift of expo. Expo's version is quite a bit different and this caused the config plugin to fail. For config plugins it's necessary to use the template of Expo to make prebuild work correctly.

Expo SDK 52 never shipped with the swift template so this change will not break anything.

Related issues

Release Summary

Update config plugin to support Expo SDK 53

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

It's a bit difficult to test but this is what I did to validate that it works:

• Set up a new expo SDK 53 beta project
• Build the plugin
• Copied the build folder to my own project (fb-plugin)
• Added local plugin to app.json:

"plugins": {
  "./fb-plugin"
}

• run npx expo prebuild --clean
• ios/myapp/AppDelegate.Swift now has the correct imports

---

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 11, 2025 11:35pm

[CLAassistant]

All committers have signed the CLA.

[mikehardy]

seems imminently reasonable - many thanks! - do you use AppCheck at all? I imagine the AppDelegate plugin logic there will need some work too, it also has to do an import and a line addition in the application method in order to slice in our custom provider so we can support dynamic config at the javascript level...