Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

Releases: Synerise/ios-sdk

v4.14.6

26 Sep 10:26
Compare
Choose a tag to compare

[4.14.6] - 2023-09-26

Added

  • Synerise.setHostApplicationSDKPluginVersion(_:) method which specifies the version of the Synerise SDK plugin in the host application.

Changed

  • Improvements to stability.

v4.14.5

13 Sep 19:18
Compare
Choose a tag to compare

[4.14.5] - 2023-09-12

Fixed

  • Potential in-app messaging issue that could have caused blank screen after dismissing a modal displayed over an in-app message. This problem occurred in a specific view hierarchy and modal presentation style when the in-app message template was TOP_BAR or BOTTOM_BAR.

v4.14.4

31 Aug 11:00
Compare
Choose a tag to compare

[4.14.4] - 2023-08-31

Added

  • .anonymous and .google in TokenOrigin enumeration type.
  • LICENCE for the SDK.

Changed

  • ClientStateDelegate for handling client sign-in state is also invoked when a customer uses Simple Authentication.
  • The snr_notificationDidReceive(notificationInfo:) method in NotificationDelegate is also invoked in foreground state and in the host app after clicking on notification and move to app.

Changed

  • Improvements to stability.

v4.14.3

04 Aug 07:57
Compare
Choose a tag to compare

[4.14.3] - 2023-08-04

Fixed

  • The issue that could have caused incorrect sorting of in-app messages.
  • Potential issues with Simple Authentication requests.

Added

  • tags property in the ClientSimpleAuthenticationData model.

Changed

  • Improvements to stability.

v4.14.2

01 Aug 12:06
Compare
Choose a tag to compare

[4.14.2] - 2023-08-01

Fixed

  • The issue that could have caused a customer sign out in some cases when a customer context was changed.
  • Potential issues with sharing data sources related to using Synerise.setRequestValidationSalt(_:) before SDK initialization.

Changed

  • Improvements to stability.

v4.14.1

28 Jul 00:09
Compare
Choose a tag to compare

[4.14.1] - 2023-07-28

Fixed

  • Promotion model mapping caused in previous versions (3.13.2 and 3.14.0).
  • Potential issues related to validating models from the SDK due to redundant data (if result model is Dictionary).
  • AutoTracking .plain mode that sent other events than it should (now, it send only screen.view events).

v4.13.2 - REMOVED

20 Jul 22:22
Compare
Choose a tag to compare

[4.13.2] - 2023-07-20

!!! THIS VERSION HAS BEEN REMOVED DUE TO THE POSSIBILITY OF A CRITICAL ERROR !!!

Added

  • We have introduced new extra parameters within the internal screen.content event. This event is sent whenever a screen view is generated, providing information about the specific screen view such as document UUIDs, document slugs, and crucial meta parameters of a document used in a screen view.

v4.14.0 - REMOVED

12 Jul 16:57
Compare
Choose a tag to compare

[4.14.0] - 2023-07-12

!!! THIS VERSION HAS BEEN REMOVED DUE TO THE POSSIBILITY OF A CRITICAL ERROR !!!

Added

  • New authentication mechanism - Simple Authentication. It allows identification of customers without implementing more complicated processes such as RaaS, OAuth, or authenticating by third party services, for example Facebook or Apple. Simple Authentication needs only two methods - Client.simpleAuthentication(data:authID:success:failure:) to recognize a customer and Client.isSignedInViaSimpleAuthentication() to check if the customer is signed in and uses the Simple Authentication feature. The Client.signOut() method and similar methods are a common way to sign out and clear the user context.
  • We added a new Client.registerForPush(registrationToken:success:failure:) method. It is analogous to Client.registerForPush(registrationToken:mobilePushAgreement:success:failure:), but doesn't require themobilePushAgreement parameter and thanks to that, it doesn't update the customer in the database.

Changed

  • We changed the behavior when a customer context changes. Now, events that were queued before the context change are force-sent to the previous client profile.
  • Improvements to stability.

v4.13.1

29 May 08:21
Compare
Choose a tag to compare

[4.13.1] - 2023-05-29

Fixed

  • Potential issues related to banner trigger automation.
  • In-app events (inApp.capping, inApp.renderFail, inApp.controlGroup) didn't contain the variantId parameter, now it's fixed.

Changed

  • We added additional validation for the Synerise.changeClientApiKey(clientApiKey:) method. Now, you try to change the current API key to the same one, it's blocked and no action is invoked.
  • We updated terminology in header files from 'client API key` to 'profile API key'.

v4.13.0

24 May 21:34
Compare
Choose a tag to compare

[4.13.0] - 2023-05-24

Added

  • We added a new Content.generateDocument(slug:success:failure:) method. It's analogous to Content.getDocument(slug:success:failure:). The old method is deprecated. The new method generates the document that is defined for the provided slug.
  • We added a new Content.getRecommendationsV2(options:success:failure:) method. It's analogous to Content.getRecommendations(options:success:failure:). The old method is deprecated. The new method gets recommendations that are defined for the options provided.
  • We added a new Content.generateScreenView(feedSlug:success:failure:) method. It's analogous to Content.getScreenView(success:failure:). The old method is deprecated. The new method generates a customer's highest-priority screen view campaign that is defined for the provided slug.
  • We added models correlating with new methods: ScreenView, Document.

Changed

  • Content.getDocument(slug:success:failure:) is deprecated now.
  • Content.getDocuments(apiQuery:success:failure:) is deprecated now.
  • Content.getRecommendations(options:success:failure:) is deprecated now.
  • Content.getScreenView(success:failure:) is deprecated now.