Registering a File Protocol, app not receiving URI parameter as expected


#1

Hello,

I have successfully registered a file protocol for Windows and OSX in the app i am working on. In both cases, the app launches from an external link with my href, appname://

The documentation for app.setAsDefaultProtocolClient states that the URI used to open the app will be passed to it as a parameter, accessible on Windows through process.argv and on OSX through the open-url event.

In Windows, the app is launched, but i have no such parameter in argv, instead i have the path to the electron executable, and the two parameters i am calling with, app path, and one flag i am using. The URI it was originally launched from seems to be missing.

Can anybody shed any light on this?

Thanks,
Mike


#2

Nevermind, i solved this. Had the protocol configuration incorrect. It works as expected now