Skip to main content

Troubleshooting Local Testing Setup Issues

A guide for solving known issues that you might face while trying to setup the BrowserStack Local App for local testing with Live.

BrowserStack Local App Installation Issues

When installing the BrowserStack Local App on your machine, you may face issues arising from various restrictions enforced as part of your network policies. Some known issues and possible resolutions are as follows.

A security warning blocking the installation

Note: This issue/resolution applies to the Windows OS only.

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

Security warning during Local App installation

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 for 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.

App files could not be downloaded during installation

Note: This issue/resolution applies to the Windows OS only.

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

Failure to download Local App files during installation

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.

Connectivity issues after launching the BrowserStack Local App

Though a connection with the BrowserStack Local App happens automatically when you launch a Live session, occasionally you might have to explicitly connect to the Local App using the Connect button in the App UI menu.

In some cases, the Local App might fail to establish a connection to enable local testing in Live. To verify if you are connected, complete the following steps:

Step 1. Access the Local App UI in the system tray to check the current App connection status. If the current status is Connected as shown in the following screenshot, the connection is successfully established and you can continue local testing in Live. If the current status is Disconnected, click Connect to open the Local Console in your default browser.

Connecting the Local App

Step 2. The Local Console is designed to use the same access key used in an earlier connection to connect to the Local App. In case the Local Console does not connect automatically, enter the access key manually, and then click Connect. You can view the access key from your BrowserStack Account Settings by on the Settings menu-item under the Account menu on your Live dashboard.

Local Console connection page

Step 3. Verify your connection status in the App UI. If the connection fails, you might face the following error:

Local Console connection error

This error indicates the Local App was unable to connect with BrowserStack servers required for local testing to work. There may be a number of reasons why this might be happening. The following are some known issues & possible resolutions.

WebSockets traffic blocked by the network

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 whitelist 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.

Proxy server being used to access the internet

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

After you have the proxy server address & port, configure the proxy settings on the Local Console as shown in the following image. You might also need to enter the credentials if required by the proxy server.

Local Console connection page proxy details

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback

Is this page helping you?

Yes
No

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback!

Talk to an Expert
Talk to an Expert