Today we released a new version of the native Android player app (v4.4.92) and a new version of the Chrome OS app (v4.4.92).

Android 8 Oreo and SSL securityAdditions to the Android player app:

  1. Fix for Android 8 – Now the app supports Android version 8, as well.
  2. Fix for event interrupt – That means now when you use multiple events on the same Android unit, you can have one event interrupt another. Example: you have a connected liquor box, when opening its door triggers a bottle video slide on the TV display and you also have connected RFID reader, where placing objects on it triggers slides of the corresponding products. So, how will it behave now? If you keep the checkbox “Slide cannot be interrupted” unchecked, one event can override another. So if this is what you set in the playlist’s settings in your online Studio account, then imagine this scenario: a visitor comes and opens the liquor box door, then, as a consequence, the bottle video slide starts playing. But in the middle of the video, the visitor put a beer can on the RFID reader and then an information slide appears on the screen and stopping the previous video in the middle. If you do check the “Slide cannot be interrupted”, then the second part could not take place, means the beer information slide would not appear since the bottle video did not finish playing till its end.
  3. Added a setting to be able to choose SSL communication (HTTPS) on the app. Till now, the outgoing and incoming communication from the player app was regular HTTP (except from logging in to your user from the app for the one time action of choosing the screen key). Now you have a new setting called “SSL Connection” (under the “Connectivity” block of settings) which is default set to “off” (for backward compatibility). If you like SSL, just set it to “on”. This new setting was also added to the native Windows player app, which will be released next time.

Additions to the Chrome OS player app:

  1. Fix for event interrupt – same as for the Android app, explained above.
  2. Added a setting to be able to choose SSL communication (HTTPS) on the app – same as for the Android app, explained above.