I have also encountered this situation. You can see the error message from the F12 developer tools, and it appears that there is an error in how the browser is parsing the custom protocol.

I am currently using Edge as a workaround.