chrome apps
7 TopicsChrome Sign Builder: Deprecation
Further to the Help Center post, we wanted to bring up an important update regarding Chrome Sign Builder. As part of the ongoing evolution of ChromeOS and the phasing out of Chrome apps in kiosk mode, Chrome Sign Builder will soon be deprecated. What's Happening? Chrome Sign Builder, a Chrome app used to schedule and display content on managed ChromeOS kiosk devices, is reaching its end of support. This change is aligned with the broader initiative to transition from Chrome apps to more robust and modern web-based solutions. Key Dates to Remember The Chrome Sign Builder app will be removed from the Chrome Web Store at the end of ChromeOS M150. This means it will no longer be available for download or continued use beyond this point. Your Alternatives for Digital Signage We understand that digital signage is a crucial part of many organizational setups. To ensure a smooth transition, we recommend the following alternative solutions: Option 1: Partner with Comeen - Consider leveraging Comeen, a Chrome Enterprise Recommended Partner. Comeen offers a direct replacement with their web-based digital signage application, designed to meet your needs and integrate seamlessly with ChromeOS. Option 2: Manually Deploy a Web App - For those who prefer to manage solutions in-house, you can manually deploy a web app through the Google Admin console. This involves adding the URL of your chosen digital signage web application and, optionally, configuring it to auto-launch on your kiosk devices. Action Required: Deleting Chrome Sign Builder To ensure a clean transition and remove the deprecated app from your managed devices, please follow these steps: Navigate to the Google Admin console. Go to the Apps & extensions page. If Chrome Sign Builder is configured in your organization, you will see a notification banner. Proceed with deleting Chrome Sign Builder from your devices. Please note that deleting the app will also remove any associated user data upon the device's restart. We encourage you to begin planning your transition to an alternative solution well in advance of the M150 deprecation to avoid any disruption to your digital signage operations.101Views0likes0CommentsCustom Protocol Handler for Isolated Web App Not Working After ChromeOS Update (May be).
Hello, After my ChromeOS device updated on September 25, 2025 (though not certain this is the direct cause), custom protocol handlers (web+collab:// and collab://) for my Isolated Web App (IWA) stopped working. Triggering these links in Chrome no longer launches the app—they simply do nothing. This was functional until two days ago. App Type: Isolated Web App (IWA) Manifest excerpt: { "name": "someapp", "id": "/", "short_name": "some-app", "version": "0.1.0", "update_manifest_url": "https://github.com/--some-repo--/iwa-release/releases/latest/download/update.json", "icons": [ { "src": "/192x192.png", "sizes": "192x192", "type": "image/png", "purpose": "any maskable" }, { "src": "/144x144.png", "sizes": "144x144", "type": "image/png", "purpose": "any maskable" } ], "start_url": "/", "scope": "/", "display": "standalone", "display_override": ["borderless"], "background_color": "#ffffff", "theme_color": "#3B82F6", "isolated_storage": true, "permissions_policy": { "cross-origin-isolated": ["self"], "direct-sockets": ["self"], "controlled-frame": ["self"], "window-management": ["self"], "display-capture": ["self"], "all-screens-capture": ["self"] }, "protocol_handlers": [ { "protocol": "web+collab", "url": "/?data=%s" }, { "protocol": "collab", "url": "/?data=%s" } ], "launch_handler": { "client_mode": "navigate-existing" }, "window_controls_overlay": { "enabled": true } } Recent Changes Enrolled new users in Google enterprise Updated the app manifest (see above) ChromeOS device updated on 2025-09-25 Observed Behavior Protocol links for both my IWA (web+collab://) and the official ChromeOS IWA SINK app (web+cf://) no longer launch the installed apps No errors, warnings, or manifest validation issues Clicking protocol links does nothing (both in managed and unmanaged device states) What I've Tried Checked manifest and protocol handler registration Tested after app reinstall and in different device policy states Reviewed enterprise Admin Console for new/relevant policy changes Searched for protocol handler or IWA-related changelogs/updates Compared behavior with different protocol URLs and schemes Questions Is anyone else experiencing protocol handler breakages for IWAs since a recent Chrome/ChromeOS update? Have there been changes in policy, manifest format, or handler registration that could affect this? Any ideas or diagnostics for discovering if Chrome or policy is blocking/ignoring the protocol? Any leads, recent experiences, or possible workarounds would be greatly appreciatedSolved99Views1like5CommentsMy website gifs don’t work on Google Chrome browser
I’ve been coding and developing my portfolio website and decided to add gifs that loop to a couple of my webpages. When I tested my website using Google Chrome, I got a broken gifs image. But when I tested on other browsers like Safari and DuckDuckGo, the gifs seem to work just fine. I’ve checked the code for errors over and over and have not been able to find any. So I decided to push my website live in hopes that the issue would get resolved. But the issue still persists. I’ve researched and have tried resetting and updating my Google Chrome browser extension and even updated my computer for the latest iOS updates. But none of that has worked, and I’ve come to realize that the gifs don’t work on any of the Google chrome browsers that I’ve used. I’ve used the Google Chrome browser on friends and family desktop computers to see if the gifs work with no success. So I know it’s not my personal Google Chrome browser settings or computer. Can someone please help!?Solved90Views0likes1CommentIssue with Play Store Apps
Since my Chromebook updated to Chrome OS, I am unable to download apps onto my device immediately; I get a message saying that "your app will download soon" and then nothing downloads. This is causing major issues with using my Chromebook. How do I resolve this?69Views0likes2Comments