Repository navigation
feat!: take native iOS and Android 5.0 - #684
Merged
Merged
Conversation
CioFirebaseWrapper now ships in customerio-ios and is versioned with it, so the fcm subspec and the example app take it from there and the separate cioiOSFirebaseWrapperSdkVersion is gone. The Android module defaults to minSdkVersion 24, matching native Android 5.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Sample app builds 📱Below you will find the list of the latest versions of the sample apps. It's recommended to always download the latest builds of the sample apps to accurately test the pull request. Builds are in progress. This comment will be updated when they finish.
|
Shahroz16
force-pushed
the
feat/native-sdk-5
branch
from
October 26, 2026 19:01
e406c32 to
3992522
Compare
The README and the deployment-target guide still said the native SDKs support older OS versions. From 5.0.0 they require iOS 15 and API 24; the normalization helper stays because the 5.0 pods declare iOS 15.0 (below React Native's 15.1) and Jist 0.1.0 still declares iOS 13.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mahmoud-elmorabea
approved these changes
Oct 26, 2026
sydneycollins-cio
approved these changes
Oct 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
React Native 7.0.0: takes native iOS 5.0.0 and Android 5.0.0. Merging to main releases 7.0.0, and the Expo plugin follows with 4.0.0 pinning it.
Refs MBL-2394, MBL-2391.
What changes for customers
customerio-reactnative/fcm)CioFirebaseWrapper1.1.0 fromcustomerio-ios-fcmCioFirebaseWrapper5.0.0 fromcustomerio-ios, same Firebase podsThe OS minimums don't change for React Native apps. This is a major because native 5.0 brings newer Firebase, Play services and WorkManager into every app, and the iOS FCM adapter now comes from
customerio-ios. Apps that pin older versions of those update them, or stay on 6.x.Podfiles stay as they are. After upgrading, run
pod update CustomerIOonce (FCM apps:pod update CustomerIO CioFirebaseWrapper), since a plainpod installstops on thePodfile.locksnapshot of the old native pin (6.15.0 to 6.16.0 behaves the same).Changes
package.json:cioNativeiOSSdkVersionis= 5.0.0.cioiOSFirebaseWrapperSdkVersionis gone, since the wrapper is versioned with the iOS SDK now.customerio-reactnative.podspec: thefcmsubspec takesCioFirebaseWrapperat the native SDK version.README.mdand the deployment-target guide: the native SDKs now require iOS 15 and API 24.android/gradle.properties: native Android 5.0.0 and a defaultminSdkVersionof 24.CioFirebaseWrapperfromcustomerio-ios.Verification
CI builds the example app for Android and for iOS with APN and FCM on Xcode 27, builds stock React Native hosts on AGP 8 and AGP 9, and runs the scene E2E.
Locally on Xcode 27.1, the example's FCM Release build resolves Firebase 12.19 from CocoaPods, builds, and runs on an iOS 26.5 simulator. Next to React Native Firebase 26.0 (Firebase 12.15 from CocoaPods) it also builds. On 6.16.1
Podfile.locks, an FCM app upgrades withpod update CustomerIO CioFirebaseWrapperand an APN app withpod update CustomerIO; plainpod installandpod install --repo-updateboth stop on the lock.React Native Firebase 27 ships Firebase only through SwiftPM, so
fcmnext to it fails with "Multiple commands produce FirebaseCore.framework". That's the same on 6.x and stays out of this release.🤖 Generated with Claude Code