TestFlight Mobile Proxies: Beta Builds on a US Carrier Network

TestFlight distributes your iOS beta to testers, and the build then behaves according to the device's network and apparent location. US-only features, storefront-dependent screens and anything your backend gates by country are seen by US testers and nobody else, unless the device's traffic exits on a US network. A Mobile Proxies US line lets an iOS device anywhere send its traffic through a US carrier address: set the Wi-Fi HTTP proxy, or run a VLESS client such as Shadowrocket for an all-traffic tunnel including UDP. The line's exit IP and rotation are in an API for your test logs.

What a TestFlight build sees from a US carrier address

Your own backend's geo gates and feature flags, evaluated against a US mobile address. Third-party SDKs that check region or connection type. Web views and embedded content that vary by location. Analytics and crash reporting pipelines that tag sessions by country and network. All of these behave as they do for your US beta testers on phones, which is the group whose bugs you are trying to catch before release.

TestFlight itself and the App Store region are account-level; the line does not change which store an Apple ID uses. It changes the network the installed build runs on.

Two ways to route an iOS device through the line

Wi-Fi proxy: in the Wi-Fi network's settings, set HTTP proxy to manual with the line's host, port, username and password. Most app traffic follows; some SDKs and UDP paths bypass it. VLESS client: import the line's vless:// link from the dashboard into Shadowrocket or a similar client and enable it. All traffic, including UDP, goes through the line, and the device behaves like a phone on that carrier network.

For QA, the VLESS route is the more faithful one. Verify by opening an IP echo page in Safari before running the build; the address should match ip from GET /proxy/status for the line.

A test matrix across carriers and metros

Buy a line per carrier if your users are split across AT&T, T-Mobile and Verizon, or one line and move it between metros for free when geography is the variable. 4G reads up to 25 Mbps download and 5G up to 50 Mbps; use both to see the range your users have. Data is not metered, so a build that syncs large assets is not a cost question.

Log the exit IP, carrier and metro from the API with each test session and attach it to the TestFlight feedback or your bug tracker.

Provisioning a test iPhone from one link

phone_profile_link in GET /proxies/my is a signed subscription URL for phone proxy apps. Add format=shadowrocket and the app receives this line live, so a new password or a moved port arrives on its next refresh rather than through a tester retyping values. It needs no API key, stops working when the licence expires and carries the login, so send it to testers privately.

Remember which traffic follows which route. A Wi-Fi proxy setting covers URLSession, but code using raw sockets ignores it; the tunnel covers both. Note in the TestFlight feedback which one the tester used. One line per tester keeps each feedback report tied to one address.

Rotation and terms

Rotate between sessions by API or by the line's rotation link, and confirm the new address in Safari before the next session. Rotate during a session only when you deliberately want to test your app's handling of a network change.

Use your own builds, your own Apple developer account and your own testers within Apple's terms. The line is a network for testing, not a way to alter storefront or account region.

Setting up a TestFlight proxy on Mobile Proxies US

1. Buy a line on the carrier your testers use most, in a US metro.
2. On the iOS device, set the Wi-Fi HTTP proxy to the line or import the vless:// link into Shadowrocket.
3. Open an IP echo page in Safari and confirm the address matches ip from GET /proxy/status.
4. Install the TestFlight build and run the US-specific test cases; log exit IP and carrier with each.
5. Rotate between sessions; move the line to another metro for free to cover a second state.

TestFlight proxy questions