[🐛] For IOS react-native-firebase will use :linkage => :dynamic for SPM But this library use :linkage => :static

[jihokim2]

What happened?

I want to use react-native-firebase and react-native-google-mobile-ads.

However, Firebase has announced that future iOS support will be provided through Swift Package Manager (SPM) only, and CocoaPods support will be discontinued.

Since react-native-firebase currently relies on use_frameworks! :linkage => :static, it is difficult to migrate to an SPM-based setup while using both libraries together.

Would it be possible to support this use case?

This also seems to be related to the discussion in react-native-firebase issue #9140:
invertase/react-native-firebase#9140

Platforms

Only on iOS

React Native Info

System:
  OS: macOS 26.6
  CPU: (8) x64 Apple M1 Pro
  Memory: 30.30 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 24.15.0
    path: ~/.nvm/versions/node/v24.15.0/bin/node
  Yarn:
    version: 1.22.22
    path: /opt/homebrew/bin/yarn
  npm:
    version: 11.12.1
    path: ~/.nvm/versions/node/v24.15.0/bin/npm
  Watchman:
    version: 2023.02.27.00
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /Users/jhkim/.rvm/gems/ruby-2.7.4/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 25.5
      - iOS 26.5
      - macOS 26.5
      - tvOS 26.5
      - visionOS 26.5
      - watchOS 26.5
  Android SDK:
    Android NDK: 22.1.7171670
IDEs:
  Android Studio: 2026.1 AI-261.25134.95.2612.15914620
  Xcode:
    version: 26.6/17F113
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 21.0.10
    path: /opt/homebrew/opt/openjdk@21/bin/javac
  Ruby:
    version: 2.7.4
    path: /Users/jhkim/.rvm/rubies/ruby-2.7.4/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 20.0.0
    wanted: 20.0.0
  react:
    installed: 19.2.0
    wanted: 19.2.0
  react-native:
    installed: 0.83.10
    wanted: 0.83.10
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: true

Are your using Typescript?

• My project is using Typescript

package.json

"@react-native-firebase/app": "^26.1.0",
    "react-native-google-mobile-ads": "^16.4.0",

app.json

{
  "name": "Test",
  "displayName": "Test"
}

ios/Podfile

android/build.gradle

android/app/build.gradle

android/settings.gradle

AndroidManifest.xml

[jaydaVis04]

Hi, I’d like to investigate this issue. My plan is to reproduce the iOS linkage problem with the current version, identify whether it comes from the podspec, framework linkage configuration, or build settings, and then add the smallest fix that works for both supported linkage modes. Is this issue still available to work on?

[mikehardy]

I think what really needs to happen here is to support SPM, similarly to how we do in react-native-firebase - and we should do that with dynamic linkage I think

(for people that need to use static linkage, they can opt to use cocoapods in the same way they can opt out of SPM in RNFB)

this issue is available to work on, but it will not be easy, if react-native-firebase is any indicator

two things are definitely true of any future state here:

• cocoapods is going read-only, so we need to support SPM
• we need to interoperate with react-native-firebase (implying dynamic linkage, I believe)