Taplytics 3.0.0 Release

Major Release Changes

Updates

Thread Safety

Big changes were made to make the SDK more thread safe! This should make the SDK more stable in cases where the methods are not being used on the main thread.

New Session Callback

We've deprecated propertiesLoadedCallback and added a new method newSessionCallback. This new method only gets called back once a new session has been started, i.e. start up, set user attributes, start new session method, or reset app user.

Usage

Taplytics.newSessionCallback { (loaded) in
    // new session has been started
}

You can also use the delegate method to accomplish the same thing:

AppDelegate.swift

class AppDelegate: UIResponder, UIApplicationDelegate, UNUserNotificationCenterDelegate, TaplyticsDelegate {

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
        Taplytics.setDelegate(self)
        ...
    }

    func taplyticsNewSession(_ loaded: Bool) {
        print("Taplytics Delegate - New Session: \(loaded)")
    }

Improvements to APIs

Improvements have been made to the robustness of caching values from previous sessions if your config call times out. Now the experience should be smoother and more consistent.