Smart TV SDK release notes
Swrve has an open source SDK repository. There are two options for downloading the latest public Swrve SmartTV SDK:
- Install the SDK using npm (node package manager).
Run the following command:npm install @swrve/smarttv-sdk
. - Download the SDK from the GitHub public repository.
For upgrade instructions, see the Smart TV upgrade guide.
Release 1.1.4
Release date: May 11, 2022
Fixes
- Resolved an issue affecting Tizen variants where device resolution information was not being returned correctly.
Release 1.1.3
Release date: April 20, 2022
Features
- Added the
inAppMessageStyleOverride
configuration option that allows you to override the in-app message container CSS style.
Fixes
- Resolved an issue where in-app messages were not appearing in certain viewport configurations.
- Resolved an issue where the SDK was not tracking impression events for message center campaigns.
Release 1.1.2
Release date: December 8, 2021
Fixes
- Resolved an issue where campaign state was not storing correctly for in-app messages.
Release 1.1.1
Release date: September 3, 2021
Features
- Added support for Universal Module Definition (UMD).
Fixes
- Handle key up event when closing an in-app message.
Release 1.1.0
Release date: October 22, 2020
Features
- Updated tracking of device OS and type for platform-specific delivery of in-app messages.
Fixes
- Updated package.json dependencies to resolve Dependabot alerts.
Release 1.0.3
Release date: February 26, 2019
Fixes
- Fixed an issue where the User Identity URL endpoint was not correct for apps using our EU stack.
Release 1.0.2
Release date: December 6, 2018
Fixes
- Resolved an issue where the Identify API was failing intermittently for multiple logins.
- Resolved an issue with user identity where the
first_session
event was being sent for existing users when they identified on a new device. - Resolved an issue where the events triggered directly after a successful Identify API call were not sending correctly.
Release 1.0.1
Release date: October 25, 2018
Fixes
- Resolved an issue where the SDK version reporting was missing crucial platform information.
- Resolved an issue were in-app messages button engagement events were reporting the wrong campaign ID.