Troubleshoot Local Testing setup issues

After you double-click the Local app installer, you might see the following security warning on your Windows machine:

Cause: This is caused due to the ClickOnce Trust Prompt Behavior on Windows. This behavior configures whether any Windows ClickOnce Application installation, such as the BrowserStack Local app obtained from a certain source, such as a website, can be installed or not.

Resolution: To fix this behavior, change a certain Windows registry using the following steps:

1. Click the Start menu, type Run, and press Enter.
2. Type regedit and press Enter to open the Registry Editor.
3. From the left navigation pane, search for the \HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\.NETFramework\Security\TrustManager\PromptingLevel registry key. If the key doesn’t exist, create the registry key.
4. Add the following String Value sub-keys to the above key to change the ClickOnce Trust Prompt Behavior:
   • MyComputer: Enabled
   • LocalIntranet: Enabled
   • TrustedSites: Enabled
   • Internet: Enabled
   • UntrustedSites: Disabled

Contact the IT administrator of your organization to resolve any issues. If you need further help, contact BrowserStack Support.

You may face the following errors during installation, indicating certain App files could not be downloaded during the installation process.

Cause: This issue usually stems from network restrictions disallowing applications to be downloaded from the the internet or accessing certain URLs used for downloading the files used during the installation process.

Resolution: You may either contact the BrowserStack Support for further assistance on this issue or use the BrowserStack Binary for your OS platform, which does not require additional installation.

Cause: If you are accessing the internet through a proxy server, configured either on the OS or the browser level, you need to enter your proxy details in the Local Console. If you are unsure whether your network settings use any proxy, use this guide to verify.

Resolution: To resolve this issue, you need to configure your proxy settings on the Local Console. To configure your proxy settings, obtain the proxy details (host, port, authentication details if the proxy requires authentication) from your network/IT team.

Complete the following steps after you enter the access key on the Local Console and see the proxy connection error:

1. For the Is your network restricted by an enterprise firewall or proxy? question, click Yes, I have a proxy.
2. On the Settings prompt, enter the proxy details and click Connect. Your proxy is configured and you are taken to the Local Console. On the Local Console, you can see the Connected status.

Cause: The Local app connects to BrowserStack servers through a WebSocket connection. For more information about how Local app connects, check out this page. Any restrictions to this traffic in the organization’s network may cause the connection to fail. Visit this page to confirm if WebSockets are working correctly in your network.

Resolution: Contact the IT team of your organization and request them to allow all traffic for the wildcard domain *.browserstack.com or explicitly allow WSS traffic on ports 80 and 443 in your network. If you need any further assistance, contact BrowserStack Support.