Custom Protocol Handler - Screenleap/support GitHub Wiki

Process

The process for sharing your screen using the custom protocol handler is as follows:

1. The user initiates a new screen share.
2. A download of the native app is initiated.
3. We wait 20 seconds after the download is initiated to give the user time to open and run the app.
4. After 20 seconds, we attempt to start the screen share using the custom protocol handler.
5. We wait another 12 seconds for API screens shares and 20 seconds for Screenleap screen shares to give the user time to allow the use of the custom protocol handler and for the app to start up. The wait is configurable using showScreenShareStartErrorDelay.
6. If the app hasn't started after the delay, we make a call to onScreenShareStartError to show the user the troubleshooting instructions with a link to manually retry the custom protocol handler.
7. After the screen share has started, we add the __aa cookie so that we can remember that the user has successfully installed the presenter app. We need to do this because web browsers do not offer any way for determining whether the presenter app has been installed or whether the user has given premission to enable the custom protocol handler. If the cookie is presenter, we will attempt to start the screen share immediately instead of initiating the download first.