Axeptio SDK 1.1.0

Axeptio Native Android SDK 1.1.0

implementation("io.axeptio:sdk:1.1.0")

Upgrading from 1.0.1

• AxeptioPermission import. Import it from io.axeptio.sdk.configuration. The 1.0.1 import from
  io.axeptio.foundation.core.config still compiles but is deprecated. Apps compiled against 1.0.1
  keep working without recompiling. After you switch imports, three patterns no longer compile:

  • assigning a list to permissions directly;
  • an empty list with no type argument, such as withPermissions(emptyList());
  • reading permissionType or androidPermission. Use manifestPermissions instead.

  See Upgrading from 1.0.1.

• INTERNET permission. The SDK now declares it, so you can remove the entry you added for it.

• R8 / ProGuard. The SDK now ships its own rules, so you can remove any -keep rules you copied
  for io.axeptio.**.

• show*() before initialize(). showConsentFlow, showConsentManager and
  showPermissionsScreen now throw SdkNotInitializedException instead of crashing the app.

Fixed

• clearConsentData() now removes every stored consent, including the IABTCF_* keys, even when it
  is called before the configuration has loaded.
• A consent submitted just before, during or right after clearConsentData() can no longer reappear
  after the clear. The same holds across a shutdown() followed by initialize().
• In the Publisher (TCF) flow, "Accept all" is no longer saved as a refusal when it is pressed before
  the vendor list has loaded. The consent screen is shown again instead.
• Consent is stored and encoded with the configuration it was given for, even if the configuration
  changes while it is being saved.
• Calling shutdown() while a consent screen is open, or during a process restore, no longer crashes
  the app. The screen closes cleanly.

Documentation and sample app

• The README now covers setup prerequisites, consentStatusFlow states and threading, the TCF
  storage keys, the network data collected (for Play Data safety) and migration from the WebView
  SDK.
• The sample app collects the consent status in a lifecycle-aware way, re-initializes without
  restarting, shows the stored consent details, and has a minified release build.