Version 26.3.0 IOS Build Error happend

[jihokim2]

Issue

---RNFBMessagingModule.mm:92:10 Cannot initialize return object of type 'ModuleConstantsJS::NativeRNFBTurboMessaging::Constants::Builder' with an rvalue of type 'ModuleConstantsJS::NativeRNFBTurboMessaging::Constants'

Describe your issue here

Project Files

Javascript

Click To Expand

package.json:

# N/A

firebase.json for react-native-firebase v6:

# N/A

iOS

Click To Expand

ios/Podfile:

• I'm not using Pods
• I'm using Pods and my Podfile looks like:

# N/A

AppDelegate.m:

// N/A

---

Android

Click To Expand

Have you converted to AndroidX?

• my application is an AndroidX application?
• I am using android/gradle.settings jetifier=true for Android compatibility?
• I am using the NPM package jetifier for react-native compatibility?

android/build.gradle:

// N/A

android/app/build.gradle:

// N/A

android/settings.gradle:

// N/A

MainApplication.java:

// N/A

AndroidManifest.xml:

<!-- N/A -->

---

Environment

Click To Expand

react-native info output:

 OUTPUT GOES HERE

• Platform that you're experiencing the issue on:
  • iOS
  • Android
  • iOS but have not tested behavior on Android
  • Android but have not tested behavior on iOS
  • Both
• react-native-firebase version you're using that has this issue:
  • e.g. 5.4.3
• Firebase module(s) you're using that has the issue:
  • e.g. Instance ID
• Are you using TypeScript?
  • Y/N & VERSION

---

• 👉 Check out React Native Firebase and Invertase on Twitter for updates on the library.

[russellwheatley]

@jihokim2 - please provide some detail, our CI passed on multiple paths (SPM, Cocoapods) + debug/release build variants.

[jihokim2]

@russellwheatley It occurred CocoaPaths and debug build variants

[mikehardy]

@jihokim2 we'll need to see a reproduction or information for a reproduction

"there was a build error", "it happened in CocoaPaths and debug build variants" is not nearly enough to go on

As an exercise: if you were a development team lead, and you had one of your developers come to you with this problem, what information would you need to help them? We also need that information. It was all requested in the issue template which you did not fill in with information

[jihokim2]

@mikehardy Thanks for the feedback — sorry for the incomplete report. Here’s the information needed to reproduce.

Environment

• Platform: iOS
• React Native: 0.83.10
• @react-native-firebase/app: 26.3.0
• @react-native-firebase/messaging: 26.3.0
• @react-native-firebase/analytics: 26.3.0
• New Architecture: enabled (newArchEnabled=true on Android; iOS using RN default New Arch for this RN version)
• Hermes: enabled
• CocoaPods: use_frameworks! :linkage => :static
• $RNFirebaseDisableSPM = true in Podfile
• iOS deployment target: 15.1
• Xcode: <FILL: e.g. 16.2 / 16.4>
• macOS: <FILL: e.g. 15.x>
• Build configuration: Debug (also fails in local Xcode build)
• Architecture: <FILL: simulator / device / both>

Exact compile error

Cannot initialize return object of type 'ModuleConstantsJS::NativeRNFBTurboMessaging::Constants::Builder' with an rvalue of type 'ModuleConstantsJS::NativeRNFBTurboMessaging::Constants'

File involved:

• node_modules/@react-native-firebase/messaging/ios/RNFBMessaging/RNFBMessagingModule.mm
  (constantsToExport / getConstants)
• Generated header expects:
  ModuleConstants<JS::NativeRNFBTurboMessaging::Constants>
• Implementation currently declares return type as:
  ModuleConstants<JS::NativeRNFBTurboMessaging::Constants::Builder>

Steps to reproduce

1. Fresh install deps (yarn install / pod install)
2. Open ios/*.xcworkspace in Xcode
3. Build Debug for iOS simulator/device
4. Build fails during compile of RNFBMessaging TurboModule constants

What we already tried

• Cleaning DerivedData / Pods and reinstalling Pods — does not fix
• Because the mismatch is in node_modules source + generated codegen headers, not just CocoaPods cache

Expected

iOS Debug/Release build succeeds with RN 0.83.10 + RNFB 26.3.0 New Architecture.

Additional notes

This looks like a TurboModule constants type mismatch between:

• pregenerated/codegen protocol (Constants)
• and implementation return type (Constants::Builder)
  Happy to test a patch or a fixed release if you have

[nabinmaityordex]

@mikehardy Thanks for the feedback — sorry for the incomplete report. Here’s the information needed to reproduce.

Environment

• Platform: iOS
• React Native: 0.83.10
• @react-native-firebase/app: 26.3.0
• @react-native-firebase/messaging: 26.3.0
• @react-native-firebase/analytics: 26.3.0
• New Architecture: enabled (newArchEnabled=true on Android; iOS using RN default New Arch for this RN version)
• Hermes: enabled
• CocoaPods: use_frameworks! :linkage => :static
• $RNFirebaseDisableSPM = true in Podfile
• iOS deployment target: 15.1
• Xcode: <FILL: e.g. 16.2 / 16.4>
• macOS: <FILL: e.g. 15.x>
• Build configuration: Debug (also fails in local Xcode build)
• Architecture: <FILL: simulator / device / both>

Exact compile error

Cannot initialize return object of type 'ModuleConstantsJS::NativeRNFBTurboMessaging::Constants::Builder' with an rvalue of type 'ModuleConstantsJS::NativeRNFBTurboMessaging::Constants'

File involved:

• node_modules/@react-native-firebase/messaging/ios/RNFBMessaging/RNFBMessagingModule.mm
  (constantsToExport / getConstants)
• Generated header expects:
  ModuleConstants<JS::NativeRNFBTurboMessaging::Constants>
• Implementation currently declares return type as:
  ModuleConstants<JS::NativeRNFBTurboMessaging::Constants::Builder>

Steps to reproduce

1. Fresh install deps (yarn install / pod install)
2. Open ios/*.xcworkspace in Xcode
3. Build Debug for iOS simulator/device
4. Build fails during compile of RNFBMessaging TurboModule constants

What we already tried

• Cleaning DerivedData / Pods and reinstalling Pods — does not fix
• Because the mismatch is in node_modules source + generated codegen headers, not just CocoaPods cache

Expected

iOS Debug/Release build succeeds with RN 0.83.10 + RNFB 26.3.0 New Architecture.

Additional notes

This looks like a TurboModule constants type mismatch between:

• pregenerated/codegen protocol (Constants)
• and implementation return type (Constants::Builder)
  Happy to test a patch or a fixed release if you have

I found a simple workaround for this issue. If I remove the ::Builder suffix from the affected ModuleConstants return types, the types match the generated Codegen types and the iOS build succeeds.

For example:

ModuleConstants<JS::NativeRNFBTurboMessaging::Constants::Builder>

→

ModuleConstants<JS::NativeRNFBTurboMessaging::Constants>

Could you please take a look and fix this in the package as soon as possible?