1.35 Release Notes
This release note describes the new build for Appspace App v1.35.
- Bug fixes and technical improvements.
|Minimum Firmware / OS Version
|Minimum Appspace Version
Dell Chromebox 3010
|Chrome OS 64
BrightSign 4K Series 2
BrightSign XD Series 2
BrightSign XT Series 3
BrightSign XD Series 3
BrightSign HD Series 3
BrightSign LS Series 3
|Samsung Smart Signage Platform (SSSP) 3.0
Chromium v 56.0.2924.59
Chromium v 61.0.3163.79
|Cisco IEC 4600 Series
|v 2.3.4b (build 5.354.406)
|Universal Windows Platform (UWP)
Microsoft Surface Pro
|Microsoft Windows 10 Pro
Samsung Tab 4
Samsung Galaxy Tab S
Firmware v 4.73.60
New Features and Enhancements
The new “Sync in Background” option during the registration process of a new device allows the Appspace App to immediately display channels via its streaming mode. Once the sync process is complete, the app restarts and displays channels via its local storage mode instead.
- APC-4287 - Appspace logo icon does not display on Appspace App for Android.
- Technical improvement to Community Cards, which fail on load as there is no failover timeout value on the card.
- AE-4404 - Unable to display any Community Card content on Appspace App 1.35.
- AE-4406 - Unable to display any Community Card content on Appspace App 1.35.
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 causes the Appspace App to reboot after a period of time, due to a potential memory leak.
It is recommended that BrightSign firmware 6.2.147 is used until the issue with the latest firmware has been resolved, which will be announced soon.
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.