Skip to main content
New Member
September 26, 2025
Solved

Custom Protocol Handler for Isolated Web App Not Working After ChromeOS Update (May be).

  • September 26, 2025
  • 2 replies
  • 1 view

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 appreciated

Best answer by J4GD33P

If your custom protocol (e.g. web+collab) stopped working after an update, it might be because some Chrome flags got reset. You can re-enable them as follows:

  1. Open chrome://flags in your browser.
  2. Search for web-app-manifest-protocol-handlers and set it to Enabled.
  3. Search for isolated and enable the required flags.
  4. Open chrome://policies and click Reload policies.

That’s it! Your custom protocol (web+collab) should now work again.

2 replies

Level 1.5: Cupcake
September 26, 2025

Faced the same, did not got any solution yet, don't know why my protocol is not working.

Lynda
Community Manager
September 28, 2025

Hi @mrutunjay and @J4GD33P thanks for getting in touch, however sorry to hear you are facing these issues. Could I ask whether you've raised a support ticket about this matter? If so, can you share the support ticket numbers here and I can ensure they are triaged and monitored accordingly?

Thanks

Level 1.5: Cupcake
September 29, 2025

Hey Lynda, thanks, it is resolved.

J4GD33PAnswer
Level 1.5: Cupcake
September 26, 2025

If your custom protocol (e.g. web+collab) stopped working after an update, it might be because some Chrome flags got reset. You can re-enable them as follows:

  1. Open chrome://flags in your browser.
  2. Search for web-app-manifest-protocol-handlers and set it to Enabled.
  3. Search for isolated and enable the required flags.
  4. Open chrome://policies and click Reload policies.

That’s it! Your custom protocol (web+collab) should now work again.

Lynda
Community Manager
September 29, 2025

Hi @J4GD33P Thanks for confirming it's resolved.

 

Can I ask whether you resolved matters by following the steps you shared above?

If so, we really appreciate you looping back to share them.

 

Also @mrutunjay can you follow the steps outlined above and see if it helps your situation? 

If not, please do raise a support case and share the ticket number here.

 

Thanks!