Fixes

1. Webapp Builds Failing on the Latest Release [ENG-4161] - We resolved an issue where newly built or republished webapps failed to load on the latest release. Existing webapps already running in production were unaffected, but any new builds did not complete and could not be previewed or deployed. Customers who experienced build failures can re-trigger the affected builds, which will now succeed without further action.

Features and Changes

1. Web Serial API Support for the PWA Player [ENG-2168] - We have added support for the Chromium browser's Web Serial API to the TelemetryTV Player PWA. Devices running in PWA mode can now communicate with serial-connected hardware (display and similar peripherals) that previously required a ChromeOS, Android, or Electron player. Serial port and command configuration is now available for PWA devices in Device Settings, with the same connection parameters and command formats used by other player platforms.

   1. Note: Requires a Chromium-based browser (Chrome, Edge). The first time a PWA device connects to a serial peripheral, it must be initiated by a user gesture, or port access can be auto-granted through Chrome enterprise policy for unattended kiosks.

2. Disable Playlist Overlays During Ad Playback [ENG-2802] - Image, HTML, and logo overlays configured on a playlist are now automatically suppressed while an ad is playing on an Ad Slot page. Previously, overlays would display on top of VAST and programmatic ad content, partially obscuring the ads. Overlays resume normal behavior on non-ad playlist pages.

Fixes

1. Group Permissions Improvements [ENG-3225] - We have made several fixes to the group permissions system to address issues affecting accounts with large numbers of groups.

   1. New groups no longer auto-grant access to existing content. When a new group is created, it now starts with no permissions on existing content folders, app folders, board folders, metric folders, or device organizations. System administrators no longer need to manually strip permissions from every existing object after creating a group.
   2. Subfolders now inherit parent folder permissions on creation. Previously, a newly created subfolder was assigned the creating user's group memberships, which could silently grant write access broader than the parent folder's restrictions allowed. Subfolders now inherit the parent folder's groups and read-only groups, and the permissions panel pre-populates accordingly when a parent folder is selected during creation.
   3. Group lists in the permissions UI are now contained within their panel. On accounts with a large number of groups, the group list could overflow its container and become unclickable without zooming out. The permissions table now constrains the list to its panel and scrolls within it.

2. Overrides Now Hide When CAP Trigger URLs Are Invalid or Empty [ENG-2151] - Overrides configured with a CAP Trigger URL now reliably hide from the device display when the URL returns no items, returns an invalid response, or fails to parse. Previously, overrides remained visible regardless of feed state, with no error available for diagnosis. Override visibility is now tracked independently from whether the override is enabled, devices only receive overrides marked visible, and fetch and parse errors are now logged for review. We have also improved CAP feed parsing. CAP 1.2 alerts are handled more reliably, and RSS-wrapped CAP feeds are now supported.

   1. Override save validation: Saving an Override with empty Name or Message fields now displays a validation warning and highlights the missing fields, instead of silently failing.

3. Restored Canva Integration After Token Expiry [ENG-3297] - Resolved an issue where Canva design operations could fail with a "Failed to get Canva design" error after a Canva session token expired. The integration now detects authentication failures, refreshes the token automatically, and retries the request. This applies to fetching designs, listing designs, creating designs, and exporting designs.

4. Upload Drawer Error After Media Processing [ENG-3299] - Resolved an unhandled error that could occur in the Upload drawer after a media file finished uploading and processing, in some cases preventing the upload-complete state from rendering correctly. Uploads now reliably reach their completed state and notify dependent UI components without throwing.

Fixes

1. Canva Integration: Migrated to Connect API [ENG-2171] - Canva has retired their legacy Button API. We have updated the TelemetryTV Canva integration to use Canva's newer Connect API. Full Canva integration functionality has been restored.
   1. Known Limitation: Designs created prior to this migration are no longer linked to Canva through the old Button API, which has been retired. As a result, the "Modify Design" button will not function for these designs. New designs created going forward are not affected.
   2. Workaround: Your original designs still exist in Canva and in TelemetryTV. To restore the "Modify Design" functionality, you can re-link the design by re-adding it from Canva through the updated integration.

Fixes

1. Memory leak on content proxy server in TelemetryTV [ENG-2903]- Resolved a memory optimization issue within the Content Proxy service. This fix prevents potential performance degradation over time and improves overall system stability.

Features and Changes

1. Support Device Identifier Macros in VAST URL Requests [ENG-2843] -We have upgraded our VAST ad integration to support Device Identifier Macros. Previously, ad requests were identical across all screens, making it difficult for ad partners to track specific devices.

   With this update, you can now inject dynamic placeholders (such as device.serial_number, device.id or device.asset_id) directly into your VAST URLs. When an ad request is made, TelemetryTV automatically resolves these macros to the specific device's details.

   For example:

   • Example Configuration: https://adserver.com/vast?device_id={{device.serial_number}}

     • Resulting Request: https://adserver.com/vast?device_id=SN123456789

Fixes

1. Fix Duplicate Device Notification [ENG-2600]- Resolved an issue that caused duplicate notifications to be sent when a device went offline. Users will now receive a single, accurate notification per offline event.

Features and Changes

1. Yahoo Stock APP returns 500 [ENG-1595] - The Yahoo Stock app was encountering errors, preventing stock information from displaying. To resolve this, a different stock app is being used to utilize a new, reliable data source, ensuring stock information displays correctly again.
2. Implement VAST Tracking Support (Impressions, Errors, and Events [ENG-2617] - Added support for VAST tracking events, error, and click tracking elements. The player now automatically communicates ad impressions, playback progress, and errors to third-party ad servers, ensuring your ad partners receive accurate performance data.

Fixes

1. Overrides Not Hiding When CAP Trigger URL is Invalid or Empty [ENG-2151] - When a CAP Trigger URL returned an empty feed or invalid data, Overrides remained displayed on players even when they shouldn't have been. The Admin Settings logs showed no errors, leaving users with no way to diagnose why their CAP-triggered Overrides weren't working correctly. The system lacked validation to determine whether a CAP URL was providing valid data.

   We've improved how the platform handles invalid or empty CAP (Common Alerting Protocol) Trigger URLs for Overrides. The system now validates CAP feeds and provides clear feedback when issues occur.

2. [TelemetryTV] Ad Campaigns - Not Exporting All Bug [ENG-2245] ixed a bug affecting the "Export All Campaigns" feature where the export process would fail to complete for some users. The export function now runs successfully and includes all advertising campaigns.

Fixes

1. Duplicate asset_id when selecting devices [ENG-2546] - We have resolved an issue where users encountered errors when selecting a device if a duplicate asset_id was assigned through Google Admin or TelemetryTV. This update removes uniqueness validation for asset_id during device updates, allowing duplicate IDs within the same account.

Features and Changes

1. Support for Asset ID on All Device Types[ENG-1448] – An editable Asset ID field has been added for all non-ChromeOS devices, allowing administrators to manage unique identifiers directly within the Device Management page. Previously, only ChromeOS devices supported Asset IDs (managed through Google Admin).
   1. The Asset ID field is now available for Android and other non-ChromeOS devices.
   2. Users with access to devices can manually assign or modify Asset IDs through the Administrator Interface by selecting a device and editing its settings.
   3. This enhancement enables additional device identifiers.
   4. Note: This update does not affect ChromeOS devices or their existing Google Admin Asset ID integration.

Fixes

1. Inaccurate media file counts[ENG-2091] - Some accounts displayed incorrect media counts, causing them to hit the media limit even though they had fewer items uploaded. This was due to inaccurate playlist association data in the media repository, which inflated the total count. The calculation logic has been updated to correctly reflect each media item’s actual usage, ensuring that all media counts now accurately match the number of uploaded files within account limits.
2. Ad Campaign “Export All”[ENG-2245] - The “Export All” feature for ad campaigns was failing to complete due to timeouts. The export query and timeout threshold have been optimized to ensure that full ad campaign exports now complete successfully. This fix applies only to the “Export All” functionality and does not affect other export features.
3. Improved Validation and Logging for CAP Trigger URLs[ENG-2151] - Previously, TelemetryTV allowed non-CAP protocol URLs to be entered when configuring CAP Trigger Overrides. These invalid URLs were accepted without clear error messages, which could cause unexpected display behavior. CAP Trigger URLs are now properly validated to ensure only valid CAP feeds are accepted. In addition, the Admin App’s Settings log area now provides detailed error messages when CAP data retrieval or parsing fails, giving administrators clearer insight into any issues.

Features and Changes

1. Ad Campaign Macro Download (ENG-1146) - We have added the ability to download all ad campaigns with a single button, for customers who have many add campaigns and currently need to download them one at a time. Adding them all at once saves time and is more efficient. Now all ad campaigns are downloaded at once as separate .CSV files.
2. Offline Device Notifications (ENG-1143 - We have improved the notification system to notify users of their organization or other organizations if devices go offline for an extended period of time. Previously the device notification system could only be enabled on the device level. Notifications were sent each time a device went offline for more than 60s. Notifications were only able to send all notifications or send none for each notification method and there was no delineation per device or organization.
   The current notification system was not typically working well for deployments at scale. Users now have the ability to change the time interval for:
   1. How long a device is offline
   2. When a notification is sent out (24 hours)
   3. The ability to set recipients of notifications per device organization or per device
3. Tap Interaction (ENG-1144) - Previously it was not possible to trigger tap interactions using a mouse click or remote selection. We have updated the system to allow "Tap Interaction" to be triggered on devices by clicking with a mouse or selecting using a remote. It is now possible to trigger tap interaction with a mouse click or with a remote.
4. Device Report Export Improvements (ENG-1121) - Improvements are required to the Device Export Feature to capture more information from devices on customer's accounts. Currently the Device Report Export supports the following fields:
   • ID
   • Asset ID
   • Name
   • Status
   • Last Seen
   • Location
   • Playlist
   • Screen Orientation
   • Network SSID
   • Description
   • Errors
     These fields are helpful, but more information is needed that can be used for health monitoring and troubleshooting purposes. We have added the following fields to Device Report Feature:
   • System Information
   • Operating system
   • TelemetryTV Player Implementation/ API Enabled (PWA, Electron, Android Play Store, or Side Load)
   • Browser used
   • Device Model
   • Device Serial Number
   • Versioning Information
   • Operating system
   • Player
   • App
   • Browser
   • Cache Quota Information
   • Connection Type
   • Network SSID

Fixes

1. Device Notification Webhooks (ENG-1770) - There were two issues that could occur around device notifications:
   1. It was possible to have no offline notification generated when a device went offline.
   2. It was possible to have an offline notification generate when a device was still online.\
      
      Both of these conditions have been fixed in our latest release so that if a device goes offline, then an offline notification is always triggered, and it is not possible to get a false offline notification when a device is still online.

Features and Changes

1. Webhook URL Character Limit (ENG-1848) - Previously the character limit was 255 for the Webhook Notification field. The character limit has now been expanded to 350 characters.

Fixes

1. Uploader Only Permission Broken (ENG-1339) - When you created a with "Uploader only" permissions, you should have been able to select the folder and upload your media. Instead it was not possible to upload media at all. This has been fixed and now you can select the folder and upload media as required.