chromeos versions
6 TopicsCustom 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 appreciatedSolved204Views1like5CommentsMastering ChromeOS versions
Hello everyone! We all know how crucial it is to keep your ChromeOS devices running smoothly across anenterprise, especially with different versions deployed. Today, I want to highlight a fantastic, often underutilized, resource that can be a real game-changer for troubleshooting: chromiumdash.appspot.com/serving-builds?deviceCategory=ChromeOS It's packed with information that can help you quickly identify and resolve issues you might encounter. How can this website help you troubleshoot across different ChromeOS versions? Pinpoint Build Information: Ever wondered exactly what build your users are on, or what the latest stable, beta, or dev builds are for a specific device? This site gives you that information at a glance. Knowing the exact build can help you verify if a known bug has been fixed in a newer version, or if a reported issue is specific to an older release. Track Release Channels: You can see which versions are currently "serving" on Stable, Beta, Dev, and Canary channels. This is helpful when you're testing new features or trying to understand if an issue is present across all channels or just a specific one. Identify Recent Updates: If a user reports a problem right after an update, you can quickly check what changes went into that specific ChromeOS version. This can give you clues about potential regressions or new features that might be causing the issue. Compare Versions: Having trouble with a specific app or feature on an older ChromeOS version, but it works fine on a newer one? This site allows you to easily see the differences in release numbers, helping you narrow down when a fix might have been introduced, or when a change occurred that could be impacting your users. Plan Upgrades: By understanding the different serving builds, you can better plan your ChromeOS upgrade strategies and anticipate potential issues that might arise when moving to a newer version. In a nutshell, this website provides transparency into the ChromeOS release cycle, empowering you with the data you need to confidently troubleshoot problems across your diverse ChromeOS fleet. So next time you're facing a tricky ChromeOS issue, give this site a look – it might just have the answers you're looking for!100Views0likes0CommentsChromeOS 144 Regression Third Party Apps Unable to Access Location
Hello, we have observed a regression in location tracking for third party applications after updating ChromeOS on HP Chromebook G1m 11 inch. Device details are ChromeOS version 144.0.7559.108 with previous working version 131.x on the stable channel. After upgrading from version 131 to 144.0.7559.108, third party applications are no longer able to detect or receive location data while Google Maps continues to report the correct location. This behavior was working as expected prior to the OS update, which indicates a possible regression or policy change introduced in ChromeOS 144 affecting third party application access to location services. Thanks VishalSolved78Views0likes1CommentI’m experiencing an issue on ChromeOS where, after signing in, the session occasionally resets or shows a blank screen before the desktop fully loads.
Hi everyone, I’m experiencing an issue on ChromeOS where, after signing in, the session occasionally resets or shows a blank screen before the desktop fully loads. In some cases, the device appears to authenticate successfully, but the expected environment and apps do not initialize correctly. This behavior is inconsistent and seems unrelated to network stability. Basic troubleshooting steps such as restarting the device, checking for system updates, and signing out/in again have already been attempted without resolving the issue. Has anyone encountered similar ChromeOS login or session-loading problems? Any insights on logs to review or settings that might affect session initialization would be greatly appreciated.34Views0likes2Comments