custom-protocol-detection
custom-protocol-detection copied to clipboard
ismailhabib
Chrome and custom protocol
I'm currently experiencing an issue with Chrome (build 49.0.2623.87) and a custom protocol on both Windows 8 and Windows 10.
The first time the custom protocol is used in Chrome, Chrome shows an External Protocol Request popup that ask if the user wants to 'Launch the Application' and has a check box to 'Remember my choice for all links of this type.' If the check box is selected, Chrome will open the application with the custom protocol links in the future. All fine so far.
Afterwards, if you uninstall the application and custom protocol, the failure callback function isn't called when you try to use the custom protocol. Chrome instead shows a popup 'No apps are installed to open this type of link (CUSTOM PROTOCOL)' and prompts the user to look for an app in the Windows Store. This popup steals the focus.
From my research, I did find a solution that involves editing C:\Users{USERNAME}\AppData\Local\Google\Chrome\User Data\Local State (more details here), but it would be great if this could be handled by custom-protocol-detection.
Hi @edwardstumpf @ismailhabib Have you solved this issue as i am facing the same issue with Google Chrome?
Hi @edwardstumpf @ismailhabib ,
Have you find the solution to this problem. As I am facing the same issue.
My apologies for the late response on this. I haven't been able to develop a purely JS based solution.
My solution is to use my application's uninstaller to both uninstall the custom protocol (delete its registry keys) and to remove the custom protocol's entry from Chrome's Local State file. It's not an ideal solution, since Chrome needs to be shutdown in order for the change to its Local State file to take.
so how is this solution goes on? I see the function in "protocolCheck(href, function)" will be executed no matter protocol detect successfully or with failure.
