Mobile SDK v2.0.0
Mobile SDK v2.0.0 is a major release that simplifies consent-driven integrations, adds support for fetching multiple Utiq passes.
Breaking changes
- Removed initialization completion callbacks and state APIs:
- Android:
initialize(..., successCallback, errorCallback),onInitialize(...), andisInitialized() - iOS: callback-based
initialize(...),didInitializeWithResult(...), andisInitialized()
- Android:
- Removed
clearData(),acceptConsent(),isConsentAccepted(), andcheckMNOEligibility()from the public API on Android and iOS.
New
- Added
fetchIDs()to return the available ID graph as a list ofIdConnectDatarecords, including martechpass (mtid), adtechpass (atid), attributionpass (attrid), and TTL (ttl) values where available. - Retained
fetchIdConnectData()(it will be removed in the future) as the single-record compatibility API. It delegates tofetchIDs()and returns the first record. - Added an iOS privacy manifest.
Migration notes
Before upgrading from v1.0.10:
- Remove calls to the APIs listed under Breaking changes.
- Keep SDK initialization as
initialize(...)without completion callbacks, then use the fetch APIs' success and error callbacks for operational results. - Use
fetchIDs()when the application needs all returned identifiers; avoid usingfetchIdConnectData()as it will be removed in the future. - There is no need to call
acceptConsent()the host application must have Utiq consent before callingfetchIDs()because doing this call implies that such consent is already in place (e.g. via the host application's CMP). If consent for Utiq is rejected, then callrejectConsent().
Download via Maven:
implementation("com.utiq:utiq-android:2.0.0")