Tealium Kotlin 1.7.3

ProGuard rules updated to prevent mix case class names

Tealium Kotlin 1.7.2

Disable R8's full mode to fix ProGuard issues

Tealium Kotlin 1.7.1

Core 1.7.1

• Updated targetSdk and AGP versions for Core and all modules

Tealium Kotlin 1.7.0

• Core 1.7.0
  • TealiumInitProvider added to automatically execute the minimum amount of Tealium work on the Main Thread at app launch
    • This will register for Application/Activity lifecycle events at launch
    • This allows for Tealium instances to be safely created off of the Android Main Thread.
    • Tealium instances have a grace period of 10s (by default) from launch to be created in order to ensure accurate Activity tracking
      • This time limit is configurable either by:
        • updating the content-provider's meta-data using AndroidManifest merge rules
        • or by removing it using AndroidManifest merge rules, and calling ActivityManager.getInstance(context, <timeout in seconds>) in Application.onCreate() before any Tealium instances are created.
  • Batching.batchSize now actively restricts size to be between 1 and 10
  • Dispatch.remove(key: String) method added to allow for removing data
    • this was added to the interface in a backward compatible way, but any custom implementations are advised to override the default implementation.
  • BugFix: RemoteCommands not being processed when expected
    • Remote Command processing now inline with tealium-swift
    • RemoteCommand events are now processed earlier in the dispatch process, unless explicitly forbidden by a DispatchValidator (e.g. Consent or a custom supplied DispatchValidator)
    • The exceptions to this are for Batching, Connectivity and Low Battery.
    • important - Users upgrading to kotlin-core:1.7.0 are advised to update kotlin-remotecommand-dispatcher to 1.5.0 to avoid the possibility of duplicated events
  • BugFix: Queued events sent on backgrounding sometimes caused ANRs or OOM
    • Queue dispatches are now dispatched in batches according to the configured batch size to minimize memory requirements
    • These dispatches are also processed on the Tealium processing thread.
• RemoteCommandDispatcher 1.5.0
  • RemoteCommand events no longer processed on onDispatchSend but only on onRemoteCommandSend (WebView controlled) and onProcessRemoteCommand (JSON controlled)
  • important - Users upgrading to kotlin-remotecommand-dispatcher:1.5.0 are advised to update kotlin-core to 1.7.0 to avoid the possibility of missed events
• Location 1.1.3
  • BugFix: Stopping location tracking threw exceptions under some conditions

Tealium Kotlin 1.6.1

• Core 1.6.1
  • Added proper error handling for loadFromFile in JsonLoader
• VisitorService 1.2.1
  • Added proper error handle when saving VisitorProfile

Tealium Kotlin 1.6.0

• Core 1.6.0
  • HttpClient now supports only retrying on retryable response codes.
  • BugFix: ResourceRetriever refresh interval affecting library settings being fetched too often
  • BugFix: Reinstated missing ResourceEntity class
  • BugFix: Remotely configurable options for LogLevel and the enabling/disabling TagManagement/Collect module are now supported
• RemoteCommandDispatcher 1.4.0
  • Adding a RemoteCommand with a remote URL config, now supports falling back to loading from an Asset names {command id}.json on the first launch.
  • if a file name is also provided, then it will use that name to lookup the Asset
  • It is also now safe to omit the .json extension on the filename parameter when adding a new remote command, though the .json extension of the actual file should still be present.
  • BugFix: Refresh interval was not being adhered to
  • Note - com.tealium:kotlin-core module dependency minimum raised to 1.6.0
• TagManagementDispatcher 1.2.2
  • WebView is refreshed on new session to ensure latest IQ configuration is available.

Tealium Kotlin 1.5.5

• BugFix: proguard adjustment resolve missing BatchDispatch$Companion class.
• Minor lint warning fixes

Tealium Kotlin 1.5.4

• Core 1.5.4
  • Session Data Expiration BugFix: fixes an issue whereby session scoped data may not be expired on launch
  • Event Router events Buffering: buffers events until sdk is ready so events are not missed during startup
  • Database Lock crash BugFix: Some uncaught exceptions in persistence led to possible crashes
  • ProGuard rules updates to reinstate incorrectly obfuscated BatchDispatch class
• AdIdentifier 1.1.2
  • BugFix: DataLayer writes moved onto Tealium background thread

Tealium Kotlin 1.5.3

• Database Bug Fix: add database status check before performing writable actions, and allow event queueing until database is fully operational
• Library Settings Bug Fix: update how remote settings were fetched and saved
• Module Manager Bug Fix: update to thread-safe collection

Tealium Kotlin 1.5.2

Connectivity Collector BugFix: fixes an issue in the event where there is a blank string returned from telephonyManager.networkOperator

Deep Link Reporting BugFix:

• Deep Link handling limited to Activities launched with Intents where action == Intent.ACTION_VIEW
• Empty Uris are ignored, and deep links that match what is already stored is a no-op
• Handling pushed onto Tealium background thread.