v4.17.0

[4.17.0] - 2024-04-26

Fixed

• Some potential issues with retrieving system push consent by the SDK. The SDK set the constent to false when the general consent for the application was enabled, but at least one of the following options was disabled: alerts, sounds, badges.

Added

• Synerise.settings.tracker.eventsTriggeringFlush option in settings to let you set the list of event actions which will trigger instant sending of all events in the queue. The default array contains only push event's actions.

Changed

• All events connected with push campaigns will flush the queue and send events immediately.
• Improvements to push notifications registration.
• Improvements to stability.

v4.16.1

[4.16.1] - 2024-04-09

Fixed

• Nullability of clientId property in the Token model.

v4.16.0

[4.16.0] - 2024-03-25

Changed

• Improved mechanism for checking capping in in-app messages. The number of views no longer resets when the account's UUID changes.

Changed

• Improvements to stability.

v4.15.0

[4.15.0] - 2024-03-06

Added

• Global Control Group support for in-app messages. From now on, you can use this feature in in-app messaging communication. This lets you take your marketing efforts to the next level and provides a solid foundation for accurate measurement of campaign effectiveness. Read more at https://hub.synerise.com/docs/settings/configuration/global-control-group/.
• We added a new Client.authenticate(tokenPayload:authID:success:failure:) method. This method signs in a customer in with the provided token payload.
• We added a new Client.getUUIDForAuthentication(authID:) method. This method retrieves the current UUID or generates a new one from a seed (authId).
• clientId property in the Token model.

Changed

• We added additional validation for the Synerise.initialize(clientApiKey:) and Synerise.initialize(clientApiKey:baseUrl:) methods. Now, if you try to initialize the sdk when it's already running, the method is blocked and no action is invoked.
• Improvements to stability.

v4.14.12

[4.14.12] - 2024-02-27

Fixed

• Some potential issues with notification processing in NotificationServiceExtension.

Added

• Synerise.settings.sdk.localizable option in settings to let you localize some strings displayed by the SDK.

Changed

• Improvements to stability.

v4.14.11

[4.14.11] - 2024-02-06

Fixed

• Issue with non-scrolling in-app messages.

Changed

• The delegate method snr_registerForPushNotificationsIsNeeded() is invoked when the SDK is initialized completely.
• When the Client.registerForPush(registrationToken:mobilePushAgreement:success:failure:) method fails, it invokes the snr_registerForPushNotificationsIsNeeded() delegate method after a short delay.

Changed

• Improvements to stability.

v4.14.10

[4.14.10] - 2023-12-22

Added

• Swift Package Manager (SPM) support.

v4.14.9

[4.14.9] - 2023-12-04

IMPORTANT:
Due to changes in the handling of actions for URLs and deep links in Synerise campaigns, we strongly recommend comparing your configuration with the SDK documentation. Review the changes from the previous SDK version integrated into your application here:
https://hub.synerise.com/developers/mobile-sdk/campaigns/action-handling/

Fixed

• Issue with location of some SDK files in the Documents directory. The old location caused the SDK files to be visible in the shared documents directory if the host application file sharing was enabled.
• Potential issue with native notification buttons when Simple Push campaign contained Rich Media (Single Media) or had a custom notification category identifier.

Changed

• Improvements to stability.

v4.14.8

[4.14.8] - 2023-11-28

Changed

• The Synerise.setRequestValidationSalt(_:) method accepts nil now. RequestValidationSalt is not required for Simple Authentication, but we recommend using it for improved security (it needs to be enabled in the Synerise portal first).

v4.14.7

[4.14.7] - 2023-10-12

Fixed

• The notificationServiceExtensionDidFailDecryptionWithError(_ error:) method in NotificationServiceExtensionDelegate was not invoked in some cases when decryption failed.
• The push.decryptionFailed event was not sent in some cases when decryption failed.

Added

• Synerise.settings.inAppMessaging.shouldSendInAppCappingEvent option in settings to enable or disable sending inApp.capping event by the SDK.

Changed

• Improvements to stability.