Network
Network settings are configured per test case under Advanced Options.
Proxy & IP Whitelisting
By default, all device traffic routes through our proxy. If your development builds connect to private servers (config servers, game servers, etc.) that require IP whitelisting, add the following IP:
54.224.51.149If you enable geolocation mocking, traffic will no longer originate from this IP. Make sure your servers can handle both if you need both features.
Non-HTTP Traffic Whitelisting
The proxy above only routes HTTP/S traffic. If your application uses additional protocols that require whitelisting (e.g., WebRTC), please also whitelist 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/29Geolocation
Geolocation mocking lets you simulate different regions for testing country-specific behavior like:
- Age gates
- Regional content restrictions
- Localized UI/pricing
- Geo-locked features
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.