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.91 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, 2025, 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.
Note
If on an Android or iOS mobile device, refer to Appspace App 8.x Release Notes for Mobile.
Note
Additional release notes for Devices & Built-In Apps:
Older versions are unsupported.
App for Devices 2.91
25 Nov 2025, Tuesday
Release Platform: All
| Features | Description |
|---|---|
| ChromeOS Version 138 Compatibility Update | The Appspace App for Devices now supports ChromeOS version 138, ensuring continued compatibility and optimal performance on the latest ChromeOS platform. |
| API Target Level Updated to 36 | The Appspace App for Devices (Android and Android TV) has been updated to target API level 36, ensuring compliance with the latest Android platform requirements and enhancing security, compatibility, and performance. |
| Automatic Device Authentication Token Recovery | Devices now automatically detect and resolve invalid authentication tokens during startup. When a mismatch is found between cached tokens and the device’s identity due to browser cache issues, token claiming conflicts, or storage problems, the system will:
This improvement enables devices to self recover from token related authentication issues without requiring manual intervention or database maintenance. |
| Configurable PWA Cache File Size Limit | A new build argument, maxFileSizeToCacheInBytes, has been introduced to allow configuration of the maximum file size that the Progressive Web App (PWA) can cache. This enhancement provides greater flexibility in managing cached content and optimizing application performance. |
| Enhanced Logging for Cordova Brother Printer Integration | The Appspace App Client now provides improved logging for the Cordova Brother Printer integration. This enhancement addresses diagnostic needs by capturing more detailed information during printing operations, facilitating easier troubleshooting and support. |
| Enhanced Network Disruption Handling for Microsoft Teams Rooms | The application now provides improved handling of network disruptions for Microsoft Teams Rooms. When a network interruption occurs and cached content is available, the app will no longer trigger the ServerUnreachable event. Instead, it will report an “Unhealthy” state during health checks, ensuring more accurate status reporting and a smoother user experience during temporary connectivity issues. |
| ARM64 and ARM7 Download Package Enhancements | A new ARM64 package has been introduced to provide optimal performance and compatibility for modern devices running Android 16 and above. Additionally, the existing ARM7 package has been updated to ensure continued support for older or legacy hardware. |
Maintenance Releases
- APC-8076 - When provisioning Zoom Rooms on Windows devices, an error message "Failed to provision device" is displayed and content does not autoplay, despite successful provisioning on Neat Bar devices.
- APC-8089 - Advanced Channel media zone background images do not display on UWP Webview2 and Windows Electron devices.
-
AE-13113 - Tizen devices running version 6.5 and later do not correctly apply portrait orientation when configured through the Appspace Console or the b2bapis.b2bcontrol.setMenuOrientation("DEGREE_90") function. This behavior is due to the absence of proper TV-to-app mappings for DEGREE_X formats, resulting in the device defaulting to landscape mode.