PSA Google Chrome pushed a breaking change in custom protocol handlers this week
Trying to save lots of time we wasted debugging this issue: If you have built an app around a custom protocol (i.e. oursoftware://do_cool_thing?callback=http://coolthingdone.com ), the roll-out of Chrome M130 breaks those URLS ( https://issues.chromium.org/issues/374691247 ). Obviously Edge and similar Chromium-based browsers are also affected
This is by design. Unless you are able to convince Google to roll back the change, you need to push an emergency update of your installer to register a different URL scheme.
Just wanted to give everyone a heads up, because this caught our support teams by surprise
This is by design. Unless you are able to convince Google to roll back the change, you need to push an emergency update of your installer to register a different URL scheme.
Just wanted to give everyone a heads up, because this caught our support teams by surprise