1.33 Release Notes
This release note describes the new build for Appspace App v1.33.
- Support for BrightSign devices with SSD storage.
- Support for Device Tasks to run OnBoot.
- Includes various improvements and bug fixes.
|Operating Environment||Device||Reference Models||Minimum Firmware / OS Version||Minimum Appspace Version|
Dell Chromebox 3010
Chrome OS 61
BrightSign 4K Series 2
BrightSign XD Series 2
|v 6.1.76||Appspace 6.0|
BrightSign XT Series 3
BrightSign XD Series 3
|v 6.2.63||Appspace 6.0|
BrightSign HD Series 3
BrightSign LS Series 3
|v 6.2.94||Appspace 6.1|
|Samsung Smart Signage Platform (SSSP) 3.0||DBE/DME/DHE/UDE-P/DME-BR series||
|v 1.2.4||Appspace 6.0|
|Cisco IEC||Cisco IEC 4600 Series||IEC-4650||v 2.3.4b (build 5.354.406)||Appspace 6.0|
|Universal Windows Platform (UWP)||
Microsoft Surface Pro
|Microsoft Windows 10 Pro||Appspace 6.1|
Samsung Tab 4
Samsung Galaxy Tab S
Android 4.4.2 KitKat
Android 6.0.1 Marshmallow
Firmware v 4.30.40
New Features and Enhancements
Support for running device tasks once only during a device reboot. To do this, add a task template to Advanced Tasks, and select OnBoot in the drop-down menu for the Only on Device Condition field. You then deploy the Advanced Task to a specific device(s).
Support for internal SSD storage on BrightSign devices such as XTx43 and XTx33 models. This option is typically used for for customer environments that have strict policy requirements, which prohibit external storage options such as SD cards.
The Appspace App installation package is extracted automatically to the BrightSign SSD storage via the SSD, USB or an SD card, and once the initial installation and registration process is complete, the App will operate solely from the SSD storage.
If an SSD storage is not detected on the BrightSign device, the Appspace App package will operate from the USB or an SD card.
BrightSign firmware 7.0.60 is required on BrightSign devices with SSD storage to utilize this feature.
- AE-3979 - RSS feed widget displays the incorrect year when the feed date uses the dd/mm/yyyy format.
Chrome App 1.33.1 will be pinned to Chrome 64 as it is the latest functional stable version of Chrome OS. Please refer to the Technical Limitation section below.
- APC-4203 - Chromebit displays incorrect IP after firmware upgrade.
- AE-4110 - Videos in Channels only play for 12 seconds before transitioning to the next video.
Technical Limitation & Workaround
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:
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.
We do not support any issues that arise on Appspace App based devices, if it’s not provisioned through CDM.