7.1.0

7.1.0 (2026-10-27)

React Native Firebase 26.1 and later on iOS

• React Native Firebase 26.1 and later adds Firebase through Swift Package Manager by default (27 has no other option), and customerio-reactnative/fcm adds it through CocoaPods, so the iOS build failed with two copies of Firebase. 6.x and 7.0.0 had the same problem.
• The new customerio-reactnative/fcm-core subspec adds no Firebase of its own and uses the FirebaseMessaging that React Native Firebase brings in. To switch, replace customerio-reactnative/fcm with customerio-reactnative/fcm-core in your app target, keep customerio-reactnative-richpush/fcm in your Notification Service Extension and the use_frameworks! :linkage => :dynamic setting React Native Firebase requires, then run pod install.
• Install @react-native-firebase/messaging as well as @react-native-firebase/app. Without FirebaseMessaging in the app, the SDK stops the app at launch. Don't list both fcm and fcm-core, because fcm brings Firebase back from CocoaPods. If you added $RNFirebaseDisableSPM = true or $RNFirebaseAsStaticFramework = true for the earlier workaround, remove both. Coming from 6.x, run pod update CustomerIO CioFirebaseWrapper once instead of pod install.
• Nothing changes for apps on fcm, apn or nopush, and the native iOS SDK stays at 5.0.0. The Expo plugin can't select fcm-core yet.
• Setup guide: https://docs.customer.io/integrations/sdk/react-native/whats-new/7.x-upgrade/#known-limitation

Features

• add an fcm-core subspec for apps that get Firebase from Swift Package Manager (#689) (195a10c)