Last updated on May 09, 2019

1.46 Release Notes

This release note describes the new build for Appspace App v1.46.


  • Support for BrightSign OS 8.0.
  • Support for dayparting in the console.

Supported Hardware

Operating Environment Device Reference Models Minimum Firmware / OS Version Minimum Appspace Version
Chrome OS Chromebox

Dell Chromebox 3010

AOPEN Chromebox

ASUS Chromebox

Chrome OS 69 Appspace 6.0
BrightSign BrightSign XT Series 3



v 6.2.147 /

v 8.0.48

Appspace 6.1
BrightSign XD Series 3



BrightSign HD Series 3



BrightSign LS Series 3 LS423
BrightSign XT Series 4 XT1144

v 7.1.65 /

v 8.0.48

BrightSign XD Series 4 XD1034
BrightSign HD Series 4 HD1024
MediaVue MediaVue SureVue

SureVue D1

SureVue D2

SureVue D4

SureVue D6

Firmware v 1.3.0

Chromium v 56.0.2924.59

Appspace 6.0
Universal Windows Platform (UWP)

UWP Tablets

Desktop PC/Laptops

Microsoft Surface Pro

Desktop PC

Microsoft Windows 10 Pro Appspace 6.1
Android Android Devices

Samsung Tab 4

Samsung Galaxy Tab S

5.0.0 Lollipop

6.0.1 Marshmallow

Appspace 6.1
iOS iOS Devices


iPad Mini

iOS 10

iOS 11

Appspace 6.1
LG SM5KC series 32SM5KC webOS 3.7 v 4.73.60 Appspace 6.2
SM5KD series 43SM5KD webOS 3.3 v 4.02.20
SM5KE series 43SM5KE webOS 4.0 v 04.01.60

New Features and Enhancements


The Appspace App is updated to support dayparting, a new feature that enables scheduling on playlist channels, available in the Appspace console. For more information, refer to Appspace 7.1 ac.4 Release Notes


We now support BrightSign’s latest OS update version 8.0. We have added backward compatibility for existing customers on BrightSign Series 3 devices. Deployments using XT, XD, HD, and LS Series 3 devices can now upgrade to OS 8.0.


If you wish to upgrade existing BrightSign devices running the Appspace App to OS version 8.0, the Appspace App must be updated to version 1.46 first. This is crucial to prevent the local storage from being wiped off due to the architectural changes of the location of the local storage in BrightSign OS 8.

We have also added support for the BrightSign XT, XD, and HD, Series 4 models. These devices may come preinstalled with OS 8.0.

Technical Limitation & Workaround


  • BrightSign XT1144 devices running firmware 7.1.65 have the following limitations:

    • Mouse cursor disappears when web content and cards are displayed in full screen.
    • Unable to play a WMV file without audio.
    • Unable to play multicast RTP streams.

  • BrightSign devices running firmware 8.0.48

    • When the aspect ratio of the playlist is set to Uniform Fill (default), video content is zoomed in and cropped, unlike the behavior in BrightSign OS 7, where video content fills the screen while maintaining its aspect ratio.

LG webOS

  • The device may crash and reboot, after several playbacks of multiple cards in a channel playlist when in interactive mode.

  • Below is a list of LG webOS 4.0 issues that occur when Appspace App is in interactive mode:

    • A UI alignment issue when scrolling up or down; the channel group and channel name texts are not aligned at the bottom of the thumbnail image.

    • Flickering issues occur during the following instances:

      • When loading video after an image playback.
      • When channel playlist aspect ratio is set to Uniform.

    • Keyboard and mouse intermittently get disconnected or do not function when navigating channels.

    • Back button on the remote control does not function in the Device info page.

Universal Windows Platform (UWP)

  • Devices updated to Windows 10 version 1803 (OS build 17134.48) are unable to register Appspace App.

    We recommend updating to the latest Windows 10 version 1803 (OS build 17134.122) or higher, to ensure UWP devices work seamlessly with Appspace App.

  • A cursor is displayed and does not disappear when a mouse is connected to the device, even when not in use. This is an OS limitation, where the UWP releases the cursor control back to the operation system, instead of the App, when there is switching between channel content, or web views.

    We recommend disconnecting the mouse when not in use, until this is resolved.