1.43 Release Notes
This release note describes the internal build for Appspace App v1.43.
|Operating Environment||Device||Reference Models||Minimum Firmware / OS Version||Minimum Appspace Version|
Dell Chromebox 3010
|Chrome OS 64||Appspace 6.0|
BrightSign 4K Series 2
BrightSign XD Series 2
|v 7.1.65||Appspace 6.0|
BrightSign XT Series 3
BrightSign XD Series 3
|v 7.1.65||Appspace 6.1|
BrightSign HD Series 3
BrightSign LS Series 3
|v 7.1.65||Appspace 6.1|
|BrightSign XT Series 4||XT1144||v 7.1.65||Appspace 7.0|
Chromium v 56.0.2924.59
Chromium v 61.0.3163.79
|Universal Windows Platform (UWP)||
Microsoft Surface Pro
|Microsoft Windows 10 Pro||Appspace 6.1|
Samsung Tab 4
Samsung Galaxy Tab S
Firmware v 4.73.60
This is an internal build focused on research and development.
- AE-4903 - Cards not displaying correctly on mobile devices.
Technical Limitation & Workaround
- Devices running Android 4.4.2 and below, do not contain the required OS requirements to handle the video buffering improvement needed for seamless video transition playback.
BrightSign firmware 7.0.60 causes the Appspace App to reboot after a period of time, due to a potential memory leak.
Please upgrade the BrightSign firmware to version 7.1.65 to resolve this issue.
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.
Chrome OS devices that have been recently updated to version 65 experience display/video issues. This is due to a bug that exists in Chrome OS 65.
Please follow the following workaround to enable the Appspace App to continue to work seamlessly:
- We recommend pinning Chrome based devices at Chrome OS version 64 for Appspace App to work seamlessly.
- We recommend using Google Chrome Enterprise, previously Chrome Device Management (CDM) to manage your devices. We currently only support issues that arise on Appspace App if the device is managed via a CDM.
If you have devices updated to Chrome OS 65 which have not been impacted, do not reboot the device. If you have a CMS which auto reboots the device overnight, please disable the auto reboot.
While this is not yet proven, early indications have shown that a reboot triggers the failure.
If you have devices updated to Chrome OS 65, perform a manual downgrade to Chrome OS 64 using a USB recovery image. For help, please refer to your device manufacturer.
If you have not updated to Chrome OS 65, or if you have downgraded to Chrome OS 64, pin devices to Chrome OS 64. Configure the Chrome device setting to disable auto updates and allow Appspace App to control the Chrome OS version, as per instructions below:
Follow the instructions in the Manage Chrome device settings article: https://support.google.com/chrome/a/answer/1375678?hl=en.
To disable auto-updates, navigate to Device Update Settings, and select ‘Stop auto-updates’ in the Auto Update drop-down menu.
To allow Appspace App to control the OS version, navigate to Kiosk Settings, and select ‘Allow kiosk app to control OS version’ from the Allow Kiosk App to Control OS Version drop-down menu.
Confirm and verify the Please verify Kiosk App manifest file dialog box.
Save your settings.
Do not update to Chrome OS 65.
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.