Taplytics Release 1.10.4
-
Timeout declaration have been removed from callbacks and added as a Taplytics starting parameter
For example, you now can start Taplytics as such:
Taplytics.startTaplytics(Context, ApiKey, Options, TIMEOUT, listener)
When this timeout is reached, Taplytics will continue and ONLY use values stored on disk for the remainder of the session.
-
Improve code block timeout and cache interaction.
-
Make fewer socket connection calls on debug app startup.
-
Kickoff all variableupdated and visual editor changes with disk or default values immediately after timeout.
-
Devices which have a delay to start Taplytics (such as via segment) will now track the main activity start more consistently.
-
Debug devices which time out can now kick off pairing without needing to restart the app.