v1.1.0

Change Log

Summary

Outlines the changes introduced in the latest version of the project.

Changes

Updated Transcend Version

• Upgraded to Transcend v1.1.0.
• Implemented consent synchronization across devices, including web and mobile platforms.

Deprecated Methods

The following methods are deprecated and should be avoided in favor of newer alternatives:

• public init(transcendConsentUrl: String, isInit: Bool, didFinishNavigation: ((Result<Void, Error>) -> Void)?)
• public init(transcendConsentUrl: String, isInit: Bool, _ syncDomains: [String], didFinishNavigation: ((Result<Void, Error>) -> Void)?)
• public init(transcendConsentUrl: String, isInit: Bool, onCloseListener: ((Result<Void, Error>) -> Void)?)

New Features and Improvements

• TranscendWebViewUI now supports initialization with TranscendCoreConfig, incorporating all necessary configurations.
• By default, synchronization across devices is now enabled when TranscendCoreConfig is instantiated, requiring the inclusion of the token property. This token can be generated by following the steps outlined here.
• Users are encouraged to migrate to using the following TranscendWebViewUI instances:
  • To create a UI instance: public init(transcendCoreConfig: TranscendCoreConfig, onCloseListener: ((Result<TrackingConsentDetails, Error>) -> Void)?)
  • To create an API instance without UI rendering: public init(transcendCoreConfig: TranscendCoreConfig, didFinishNavigation: ((Result<Void, Error>) -> Void)?)
• The onCloseListener closure now returns User Consent details. Previously, users had to retrieve data using TranscendWebView.transcendAPI.webAppInterface.getConsent(), which is no longer necessary.

Usage Guidelines

Ensure to update your implementation to utilize the latest features and avoid deprecated methods for smoother integration and improved functionality.