Release Notes

Below is a complete list of changes for each release of the Cordova library. See the file CHANGELOG.md for full list of changes.

It is strongly recommended that you remove and re-add the plugin from your project for the 1.1.1 release.

1.1.5

• Updated iOS dependency to fix code signing issue for TealiumIOSLifecycle framework.

1.1.4

• Upgraded core SDKs to tealium-android 5.9.1 and tealium-ios 5.8.1
• Updated Android Gradle files to use https to support AndroidX

1.1.3

• Upgraded core libraries to latest versions.

1.1.2

• Fixed “Diamond Operator” issue

1.1.1

The plugin package name changed from com.tealium.cordova.v5 to tealium-cordova-plugin.

To remove earlier plugin versions, run the following command:

cordova plugin rm com.tealium.cordova.v5

1.1.0

The 1.1.0 release changed some API behavior. Test the following items after upgrading:

• If you were previously using the addVolatile and addPersistent methods, then ensure that you are only storing supported data types specified earlier.
• To improve performance on iOS, the plugin now runs most of its code on a background thread, except for the initialization method. Report any issues via the GitHub issues page.
• The variable cordova_lifecycle, which was previously sent with all lifecycle events, has now been removed. If you still require this variable, create it again by using a Set Data Values extension in Tealium iQ, with a rule if lifecycle_type is populated to create the variable and add it to all lifecycle events.
• On iOS, lifecycle sleep events are now tracked as soon as the user either puts the app into the background, or begins to close the app completely. This means when the user brings up the task switcher while an app is running by pressing the home button twice, a sleep event is generated. If the user cancels the action and goes back into the app, a corresponding wake event is generated. Previously, sleep events were only created when the user had finished backgrounding the app (by single-press of the home button, or switching to another app). This behavior matches the existing behavior on Android. Be aware that this may cause an increased amount of sleep events to be recorded in your analytics tools, but the numbers are technically more accurate