Repository navigation
fix: update native SDKs to iOS 4.12.3 and Android 4.25.2 - #680
Conversation
- iOS: 4.12.0 → 4.12.1 - Android: 4.25.0 → 4.25.2 🤖 Automated update with compilation verification
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.
|
mahmoud-elmorabea
changed the title
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 92cdbaa. Configure here.
| "./package.json": "./package.json" | ||
| }, | ||
| "cioNativeiOSSdkVersion": "= 4.12.0", | ||
| "cioNativeiOSSdkVersion": "= 4.12.3", |
There was a problem hiding this comment.
Wrong iOS native SDK version
High Severity
This change sets cioNativeiOSSdkVersion to = 4.12.3 after the PR had aligned on 4.12.1, which is what the title, release notes, and the latest customerio-ios GitHub release describe. Podspecs pass that value as an exact CocoaPods constraint for every CustomerIO/* dependency, so a version that is not published yet can break pod install for iOS apps using this package.
Reviewed by Cursor Bugbot for commit 92cdbaa. Configure here.
Shahroz16
left a comment
Shahroz16
left a comment
There was a problem hiding this comment.
Looks good. 4.12.3 is on trunk and 4.25.2 on Maven Central, so Cursor's comment is outdated. Could the release notes mention that JS-initialized apps will now track Application Installed/Updated/Opened, and that an NSE using an sk_ key won't initialize?
## [6.15.1](6.15.0...6.15.1) (2026-10-23) ### Bug Fixes * update native SDKs to iOS 4.12.3 and Android 4.25.2 ([#680](#680)) ([3589eda](3589eda))
Apps that initialize the SDK after launch can miss lifecycle events, and the iOS Notification Service Extension needs the latest proxy and API-key fixes. This PR pins iOS 4.12.3 and Android 4.25.2 so React Native apps receive all of those native fixes.
MessagingPushConfigBuilder.apiHost(...)in the notification service extension (native PR #1357).sk_secret keys in the notification service extension (native PR #1362).The native fixes are consumed through the dependency pins; no JavaScript API change is needed. Expo exposes the NSE proxy setting in customerio/customerio-expo-plugin#427, which must pin the React Native version published from this PR before it is merged.
Validation: TypeScript, ESLint, all 34 unit tests, and
npm pack --dry-runpass locally. Native sample app builds run in CI. Thefix:title and commit make this a patch release under the repository's semantic-release configuration.