7.0.0

7.0.0 (2026-10-26)

⚠ BREAKING CHANGES

• take native iOS and Android 5.0 (#684)

Migrating from 6.x

• React Native's own minimums (0.77+, iOS 15.1, API 24) already cover native iOS and Android 5.0, so your deployment target and minSdkVersion can stay. The module's default Android minSdkVersion is now 24.
• iOS: after upgrading, run pod update CustomerIO in ios/ once (FCM apps: pod update CustomerIO CioFirebaseWrapper). A plain pod install stops on the 6.x versions in Podfile.lock, and pod repo update doesn't help. Your Podfile stays as it is, except Live Activities apps, which change the widget extension's CustomerIOLiveActivitiesTemplates and CustomerIOLiveActivitiesAttributes pods to 5.0.0.
• iOS FCM: CioFirebaseWrapper now comes from customerio-ios and is versioned with it; the customerio-reactnative/fcm subspec still installs it with FirebaseMessaging from CocoaPods.
• Android builds need compileSdk 36 and AGP 8.9.1 or later (AndroidX Core 1.17, already the case in recent 6.x). React Native 0.81 and later templates meet this; apps from 0.77 to 0.80 templates raise them.
• Android: native 5.0 brings firebase-messaging 26, play-services-base 18.11 and WorkManager 2.12. If your app pins older versions of these, update them.
• Known limitation, same as 6.x: React Native Firebase 26.1 and later adds Firebase through Swift Package Manager by default, and customerio-reactnative/fcm adds it through CocoaPods, so the iOS build fails with two copies of Firebase. 7.1.0 adds the customerio-reactnative/fcm-core subspec for these apps, including React Native Firebase 27; see the 7.1.0 release notes. If you stay on 7.0.0 with React Native Firebase 26.x, add $RNFirebaseDisableSPM = true to your Podfile before any target block, with static frameworks and $RNFirebaseAsStaticFramework = true.

Features

• take native iOS and Android 5.0 (#684) (c16b1d5)