These release notes provide information on the new features, newly supported devices, enhancements, resolved escalations, and bug fixes completed in the Appspace App version 2.93 for purpose-built industry-standard devices (such as Appspace for Devices on Android and iOS tablets, and the Appspace app on Chrome OS, Google Meet, BrightSign, Cisco, and Crestron devices), ideal for signage and video walls.
Important
Beginning January 1, 2026, Appspace will implement a new Device App Version Lifecycle Policy to ensure optimal performance, security, and feature compatibility. This policy introduces a 9-month rolling support window for Appspace device apps.
To learn more about this policy and how to keep your devices updated, please refer to the Appspace Device App Version Lifecycle Policy in the Appspace Knowledge Center.
Prior version release notes for Devices & Built-In Apps:
Older versions are unsupported.
Note
If on an Android or iOS mobile device, refer to Appspace App 8.x Release Notes for Mobile.
App for Devices 2.93
28 January 2026, Wednesday
Release Platform: All
| Features | Description | ||||||
|---|---|---|---|---|---|---|---|
| Emoticon Support in Microsoft Teams Rooms (MTR) | Appspace console now provides full support for emoticons in MTR room names. This update ensures that emojis are rendered consistently across the entire platform, including device listing, analytics reports, and device info. | ||||||
| Dynamic Low Bandwidth Mode | This feature introduces a dynamic threshold for video playback on supported devices to optimize bandwidth without unnecessarily compromising the user experience. On supported devices, enabling Low Bandwidth mode does not automatically block all video playback. Instead, the system monitors the file size:
On devices that do not support local caching, enabling Low Bandwidth Mode acts as a total restriction for video playback:
| ||||||
| BrightSign SD2 (Internal SD) Storage Path Support | This introduces support for SD2 (Internal SD) as a storage option for BrightSign devices. The app now follows a specific priority order when searching for the
When updating to app version 2.93.0, customers using devices with both SD and SD2 mounted should be aware of a change in the installation destination that may affect registration status. The scenario:
| ||||||
| BrightSign 9.1.92.1 Firmware Certification Technical Info: | The Brightsigns 9.1.92.1 firmware has been fully certified to work with the Appspace App on Series 5 and 6 devices. | ||||||
| Refined Device Status For Microsoft Teams Rooms (MTR) | Device connectivity logic for MTR is updated to provide a more accurate representation of hardware states. These changes ensure that brief periods of inactivity do not trigger premature status alerts.
Key Highlights
| ||||||
| App Initialization Logic | App initialization timeouts will now only be detected if the roHtmlWidget load-finished event is not received within the specific 1-minute window assigned to the system. |
Maintenance Releases
-
APC-8190 - The Brightsigns devices with firmware 9.1.92.1 are unable to play scheduled Channel Broadcasts and instead display a blank screen, due to a console error (
$window.BSDeviceInfo is not a constructor) that prevents broadcast playback on affected devices. -
APC-8192 - The Brightsigns devices upgraded to BrightSignOS 9.1.92.1 are unable to play Advanced channels in both Single Channel and Channel Browsing playback modes, and instead only display a black screen on affected devices.
-
APC-8193 - The Brightsigns devices that have been upgraded to firmware 9.1.92.1 are unable to play Multizone channels in Channel Browsing playback mode and instead display a black screen when a Multizone channel is selected.
-
APC-8197 - The Brightsigns app rollback using the backup fails to restore custom plugin files because the
autorun-backup/pluginsfolder is created without recursively copying theplugins/subdirectories, leaving the folder empty and causing the rollback to fail due to missing plugin files.
Known Issues
- Android and Android TV devices fail to display log data when accessing the Log View from the Device Menu.