Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome and custom protocol #8

Open
edwardstumpf opened this issue Mar 28, 2016 · 6 comments
Open

Chrome and custom protocol #8

edwardstumpf opened this issue Mar 28, 2016 · 6 comments

Comments

@edwardstumpf
Copy link

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.

@ahmedtolba1984
Copy link

Hi @edwardstumpf @ismailhabib
Have you solved this issue as i am facing the same issue with Google Chrome?

@abbesch
Copy link

abbesch commented Nov 2, 2016

Did you find a solution to fix this issue?

@abbesch
Copy link

abbesch commented Nov 2, 2016

Note that on Mac OS X, this problem occurs systematically with Chrome.

@anupdhabarde
Copy link

Hi @edwardstumpf @ismailhabib ,

Have you find the solution to this problem. As I am facing the same issue.

@edwardstumpf
Copy link
Author

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.

@wiwengweng
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants