The failure callback is called even when protocol is defined

[jaimestuardo]

If protocol is defined and it is associated with an executable, browser shows an alert in order to accept or deny the execution.

I think that alert causes the timeout to occur so the failure callback is called, instead of the success callback.

Have you checked this?

I am in Google Chrome.

Thanks Jaime

[git-kks]

did you find a workaround?, i am facing the same issue in firefox v98, even after the protocol is defined and application is installed, i see open alert and failcb called