A usage guide to test your apps that need access to localhost and staging environments.
Once you’ve enabled Local Testing, access your app and interact with it, just as you would on a physical mobile device. There’s no additional setup required.
localhost
URLs
will automatically change to http://bs-local.com
. This lets us load your app
assets properly. Remember to ensure that your local server is configured to
serve requests from bs-local.com
.
You can securely test mobile apps that retrieve data from private or internal servers—on our remote mobile devices. To enable this feature, follow the steps below:
Start an App Live session. In the overhead toolbar, click on the Settings icon. In the drop-down, check Resolve all URLs through my network option option. This ensures that all the requests on our remote mobile devices are routed through your machine.
Establish the Local Testing connection with a --force-local
flag. This ensures
that all the requests on our remote mobile devices are routed through your
machine.
BrowserStackLocal --key YOUR_ACCESS_KEY --force-local
Learn more about enabling Local Testing with the Local binary here
Now, access your app and interact with it, just as you would on a physical mobile device.
You can test apps serving assets from multiple internal or public servers, with
Local Testing. For example, mobile apps that load content from
assets1.staging.example.com
, certain public servers, and
assets2.staging.example.com
.
Once you’ve enabled Local Testing, the assets will render as expected. Just access your app and interact with it, like you would on a physical mobile device.
Contact our Support team for immediate help while we work on improving our docs.