Sailthru Mobile iOS SDK 8.2.0

Features

Push Registration

Push registration in the Sailthru Mobile SDK has been updated: now the SDK will always register for remote notifications and receive a push token. Don't worry, you still have control over whether the SDK requests authorization to display alerts, sounds and/or badges - the step which requires a pop-up displayed to the user - it just means that we will have a push token for each device right from the start.
Additionally, for iOS 12+ devices if you opt out of requesting push authorization when calling startEngine, the SDK will request provisional authorization instead, allowing pushes to be sent only to the notification tray for that device. Note that a pop-up is not displayed for provisional authorization.

Note: These changes will be reflected in the app state in the following ways: after startEngine: has been called for the first time per install the UIApplication isRegisteredForRemoteNotifications method will always return YES. For iOS 12+ the UNUserNotificationCenter getNotificationSettingsWithCompletionHandler: method will return UNAuthorizationStatusProvisional as the authorization status rather than UNAuthorizationStatusNotDetermined until additional authorization is requested.

Notification Settings

The notifications settings handling has been updated to properly account for the lock screen option in the notifications options screen. An overview of the different notifications states and how they are represented can be found in the Carnival Developer Documentation.

Sailthru Mobile iOS SDK 8.1.0

Features

Custom Event Vars

Custom events provided to the platform can now contain vars, provided in a valid JSON object represented by an NSDictionary, that will be sent along with the event name. These events are now also passed through to the Lifecycle Optimiser and can be used to generate and guide flows. More details about Custom Events can be found in the Carnival Developer Documentation.

Sailthru Mobile iOS SDK 8.0.0

This release introduces some upgrades in the Sailthru Mobile SDK's networking stack, as well as some updates to how push notifications settings are represented.

Features

Push Notifications Settings - in order to properly represent the new 'Deliver Quietly' function in iOS 12 we have updated how our 'Push Enabled' state is assessed and represented. A full breakdown of the possible states and what they represent in terms of settings on the handset can be found in the Carnival Developer Documentation.

Method Removal

Synchronous methods for setting and removing Carnival Attributes ([Carnival setAttributes:error:] and [Carnival removeAttributeWithKey:error:]) have been removed. You should update calls to these methods to use the asynchronous versions ([Carnival setAttributes:withResponse:] and [Carnival removeAttributeWithKey:withResponse:]) instead.

Sailthru Mobile iOS SDK 8.0.0-beta

This is a beta release to test some upgrades that have been implemented in the Sailthru Mobile SDK's networking stack.

Method Removal

Synchronous methods for setting and removing Carnival Attributes ([Carnival setAttributes:error:] and [Carnival removeAttributeWithKey:error:]) have been removed. You should update calls to these methods to use the asynchronous versions ([Carnival setAttributes:withResponse:] and [Carnival removeAttributeWithKey:withResponse:]) instead.

Sailthru Mobile iOS SDK 7.6.0

Features

• A new method has been added to tell the SDK that it needs to sync the notifications settings on the device to the platform. Note: This will be handled automatically by the SDK under normal circumstances, this method only needs to be called if auto integration has been turned off. If auto integration is off, this method should be called after either requestAuthorizationWithOptions:completionHandler: or registerUserNotificationSettings: has been used to request notification options authorization.

Bug Fixes

• Fixed a bug that was preventing changes to the notifications settings being immediately synchronised with the platform.

Sailthru Mobile iOS SDK 7.5.0

Features

• Synchronous methods for setting and removing Carnival Attributes ([Carnival setAttributes:error:] and [Carnival removeAttributeWithKey:error:]) have been deprecated. You should update calls to these methods to use the asynchronous versions ([Carnival setAttributes:withResponse:] and [Carnival removeAttributeWithKey:withResponse:]) instead.

Sailthru Mobile iOS SDK 7.4.0

Features

Sailthru Profile Vars

Sailthru Profile Vars can now be set and retrieved through the SDK. They can be set using the [Carnival setProfileVars: withResponse:] method and retrieved using the [Carnival getProfileVarsWithResponse:] method. More details can found in the Carnival Developer Documentation.

Bug Fixes

• Collection types are now explicitly defined and will now be properly enforced when developing in Swift. They are also present as a guide for developing in Objective-C.

Sailthru Mobile iOS SDK 7.3.2

Bug Fixes

• Fixes an issue causing stale data to be sent from the device to the server.
• Fixes an issue present in version 7.3.1 that could cause notification handling issues if startEngine was called with registerForPushNotifications set to NO.
• Fixes an issue that caused the app to hang during crashes if crash handlers were enabled.

Sailthru Mobile iOS SDK 7.3.2-beta

• Experimental fix for stale device data bug

7.3.1

Bug Fixes

• Fixes an issue that resulted in duplicate influenced opens and message impressions being reported.
• Fixes an issue that resulted in direct opens being reported as indirect opens.
• Improves thread safety of CarnivalAttributes class.