Network

Network settings are configured per test case under Advanced Options.

Proxy & IP Whitelisting

If your development builds connect to private servers (config servers, game servers, etc.) that require IP whitelisting, add the following IP ranges:


103.231.42.40/29
103.231.79.40/29
209.58.137.40/29
217.112.145.88/29
149.6.5.8/29

Single IP Proxy

In cases where whitelisting the ranges above is not possible, contact us and we can route your traffic through an HTTP proxy with a single IP.

We’re currently updating our single proxy IP from 54.224.51.149 to 13.56.60.143. Please whitelist the new IP, or even better, use the full IP ranges listed above.

This proxy only routes HTTP/S traffic. Other protocols (e.g., WebRTC) will not be routed through the single IP.

We recommend whitelisting the IP ranges above instead of using the single IP proxy. The single proxy is located in US-West, and we’ve found it only delivers good bandwidth for devices in that region. Using it with devices in EU or Asia regions reduces performance. Whitelisting the ranges lets us offer the full device pool without this limitation.

Geolocation

Geolocation mocking lets you simulate different regions for testing country-specific behavior like:

Age gates
Regional content restrictions
Localized UI/pricing
Geo-locked features

Geolocation

There are two separate geolocation settings:

Setting	What it affects
IP Geolocation	Mocks the IP address location. Affects services that use IP-based location detection
GPS Location	Mocks the device’s GPS coordinates. Affects apps that use device location services

These settings are independent. Depending on how your app determines location, you may need to set one or both. For example, a web-based age gate might use IP geolocation, while an in-game map feature might use GPS.

Network Logging

Enable the Network Logging toggle to capture all HTTP/HTTPS traffic during a test run.

When enabled:

The app is re-signed to allow traffic inspection
All network requests and responses are recorded

You can find the HAR file under the artifacts in the run details.

Re-signing the app may affect certain security features or certificate pinning. If your app uses certificate pinning, network logging may cause connection failures.