iOS update 26.8

.gitignore

@@ -25,3 +25,4 @@ example/AwesomeProject/*
 example/ExpoProject/*
 hs_err_pid*.log
 replay_pid*.log
+ios/src/.build/

CHANGELOG.md

@@ -8,7 +8,7 @@
 * ! Minor breaking change ! The package now ships only the files the SDK needs at runtime; the example app, the tests and the Xcode project for manual linking are no longer part of it. It declares `react-native` as a peer dependency and needs React Native 0.62 or newer.
 * ! Minor breaking change ! The pod now makes only the bridge header and the iOS SDK's public headers public; other headers can no longer be imported from it.
 * ! Minor breaking change ! The `NotificationService` subspec no longer depends on React, and `pod 'CountlyReactNative'` installs only the `Core` subspec.
-* ! Minor breaking change ! With React Native 0.71 and newer, the pod's iOS deployment target now follows React Native's minimum iOS version.
+* ! Minor breaking change ! The pod now needs iOS 15 (tvOS 15, macOS 12, watchOS 9), the minimum of the bundled iOS SDK 26.8.0, instead of iOS 10. With React Native 0.71 and newer it uses React Native's minimum iOS version when that is higher. An app whose Podfile platform is below iOS 15, for example with React Native 0.75 or older, has to raise it; an app that has to support older iOS versions can stay on 26.1.0.
 
 * Added a `{ success, error }` result to `Countly.remoteConfig.update`, `updateForKeysOnly` and `updateExceptKeys`.
 * Added `Countly.registerForNotificationOpened(listener)`, called when the user taps a push in Android and iOS:
@@ -74,6 +74,15 @@
   * `Countly.getRemoteConfigValueForKey` and `Countly.getRemoteConfigValueForKeyP`, use `Countly.remoteConfig.getValue`
   * `Countly.remoteConfigClearValues`, use `Countly.remoteConfig.clearValues`
 
+* iOS specific changes:
+  * ! Minor breaking change ! A SIGPIPE the app neither ignores nor handles itself now ends the app after the crash is reported, as it would without the SDK. Before, the SDK reported it, kept the app running and turned automatic crash reporting off. An app that has to survive a broken pipe should ignore or handle SIGPIPE before `Countly.initWithConfig`.
+  * Added support for server requested SDK log gathering and connection tests, and for SDK behavior settings that control automatic session tracking, automatic view tracking, automatic crash reporting and Journey Trigger Views, also for the running session.
+  * Mitigated an issue where `Countly.userData.setProperty` and `Countly.userDataBulk.setProperty` with a predefined key (name, username, email, organization, phone, gender, picture, picturePath, byear) recorded a custom property of that name; they now set that field, as on Android.
+  * `Countly.setUserData`, `Countly.userDataBulk.setUserProperties`, `Countly.userData.setProperty` and `Countly.userDataBulk.setProperty` now use the iOS SDK's user property API: pending events are sent before the user details, and `null` values and nested objects are skipped with a log line instead of being sent, as on Android.
+  * The iOS SDK's default log level is now debug instead of verbose.
+
+* Updated the underlying iOS SDK version to 26.8.0
+
 ## 26.1.0
 * Added a new `Countly.sessions` interface for manual session control:
   * `beginSession()`

CountlyReactNative.podspec

@@ -8,11 +8,14 @@ Pod::Spec.new do |s|
   s.author = {'Countly' => 'hello@count.ly'}
   s.source = { :git => 'https://github.com/Countly/countly-sdk-react-native-bridge.git', :tag => s.version.to_s }
   s.requires_arc = true
-  # The privacy bundle target inherits this; React Native 0.71+ defines its own minimum, which current Xcode accepts, unlike 10.0.
-  s.ios.deployment_target = defined?(min_ios_version_supported) ? min_ios_version_supported : '10.0'
-  s.osx.deployment_target = '10.14'
-  s.watchos.deployment_target = '4.0'
-  s.tvos.deployment_target = '10.0'
+  # The bundled iOS SDK needs iOS 15, tvOS 15, macOS 12 and watchOS 9. React Native 0.71+ defines its own iOS minimum,
+  # which is used when it is higher; the privacy bundle target inherits this.
+  countly_min_ios = '15.0'
+  rn_min_ios = defined?(min_ios_version_supported) ? min_ios_version_supported.to_s : countly_min_ios
+  s.ios.deployment_target = Gem::Version.new(rn_min_ios) > Gem::Version.new(countly_min_ios) ? rn_min_ios : countly_min_ios
+  s.osx.deployment_target = '12.0'
+  s.watchos.deployment_target = '9.0'
+  s.tvos.deployment_target = '15.0'
   s.static_framework = true
   s.default_subspecs = 'Core'
 

example/README.md

@@ -158,7 +158,7 @@ STEP 3: Updating NotificationService file
 
 Note: Please make sure you configure App Transport Security setting in extension's Info.plist file also, just like the main application. Otherwise media attachments from non-https sources can not be loaded.
 
-Note: Please make sure you check Deployment Target version of extension target is 10, not 10.3 (or whatever minor version Xcode set automatically). Otherwise users running iOS versions lower than Deployment Target value can not get rich push notifications.
+Note: Please make sure you check Deployment Target version of extension target is 15.0 (the minimum of the Countly pod), not a higher version Xcode set automatically. Otherwise users running iOS versions lower than Deployment Target value can not get rich push notifications.
 
 Note: To send push messages to applications that are Debug build use Countly.messagingMode.DEVELOPMENT, for App Store built ones use Countly.messagingMode.PRODUCTION, and for TestFlight/Ad Hoc builds use Countly.messagingMode.ADHOC.
 

ios/Podfile

@@ -1,4 +1,4 @@
-platform :ios, '10.0'
+platform :ios, '15.0'
 
 target 'countly-sdk-react-native-bridge' do
   use_frameworks!