WIP fix(app, ios): generate app package module map for swift interop

[mikehardy]

Description

this should resolve an issue seen with my expo demo script where static linking wasn't working correctly via per-module directives in combination with the new prebuilt (non-static...) react-native core

Related issues

Nothing logged - this was seen with my Expo demo script which has these currently unique features, from the perspective of how we test:

• it uses the new prebuilt react-native core, which is non-static linkage (default in react-native 0.83+ / Expo 55+)
• it configures the iOS build to static link only specific modules one by one via expo-build-properties

When you do this, and you do not have this fix, you see:

[!] The following Swift pods cannot yet be integrated as static libraries:

The Swift pod RNFBFunctions depends upon RNFBApp, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies.

With this, it builds farther but still fails later which is why this is still WIP:

Specifically this import isn't found:

#import <RNFBFunctions/RNFBFunctions-Swift.h>

Note that this is not needed on current release v23.8.6, I only see this failure on main, so it isn't breaking for people...yet

Additionally, if you opt out of the prebuilt react-native core you won't see it, but everyone wants to use that and the issues in this repo about it are very active.

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

• generate packages from main via .github/workflows/scripts/create_npm_packages.sh packages ~/packages
• run https://github.com/mikehardy/rnfbdemo/blob/main/make-expo-demo.sh

You'll see the compile error I mention until you add this module map compile flag, then you'll see the swift bridging header import issue until I figure that out...

---

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 GitHub.

Project	Deployment	Actions	Updated (UTC)
react-native-firebase	Error		Mar 9, 2026 11:54pm