iOS Simulator

WePROXA can capture HTTP/HTTPS traffic from iOS Simulator, making it easy to debug your iOS app’s network requests during development.

Setup

Start WePROXA and ensure the proxy is running.
Install the CA certificate on the simulator — open Settings → CA Certificate and choose Install to booted iOS Simulators. It installs into every booted simulator at once. If one simulator rejects the certificate, the others still get it, and the message names successful installs and individual failures. Boot a simulator first; the button reports an error if none are running.
Configure the simulator proxy — iOS Simulator respects the macOS system proxy settings. When WePROXA’s system proxy is enabled, simulator traffic will flow through WePROXA automatically.
Launch your app in the simulator and start making network requests.

Viewing Simulator Traffic

Traffic from iOS Simulator appears in the request list alongside regular traffic. You can use the source view or filters to identify simulator requests.

When WePROXA can resolve the Simulator app bundle, the Apps source view can show the app’s icon next to its traffic. This makes it easier to distinguish multiple Simulator apps while debugging.

Known Apple networking services running inside a Simulator have separate names ending in Simulator and a small phone badge on their icon. This keeps, for example, a Simulator service separate from its macOS counterpart in Explorer, app-targeted rules, and SSL interception. Use the exact displayed name when targeting the Simulator service. Simulator app icons are also sized consistently with native app icons.

If a Simulator connection appears as Not decrypted: certificate rejected, select it and open the response pane. The Simulator may not trust the CA, or the app may have closed the handshake early. Learn more opens the certificate troubleshooting FAQ.

Install the certificate from an AI client

If you drive WePROXA through MCP, the same install is available as a tool call:

Call weproxa_certs_getCaInfo to confirm which certificate you are about to install — it returns the CA’s path, SHA-256 fingerprint, expiry, and whether macOS currently trusts it.
Call weproxa_certs_installToIosSimulator.

It targets the booted simulator and needs an explicit udid when several are booted. The call fails with a clear message when no simulator is booted, when the requested udid is not booted, when the CA has not been generated yet (start the proxy once to create it), or when simctl rejects the certificate. It returns the UDID, the device name reported by simctl, and the certificate path that was installed.

The certificate menu and the MCP tool list simulators and report errors the same way. They differ in one point: the menu button installs into every booted simulator, while the MCP tool installs into one and asks for a udid when several are booted.

Tips

Make sure the system proxy is enabled in WePROXA for automatic routing
If using a custom proxy configuration in your iOS app, point it to WePROXA’s proxy address (shown in Settings)
All WePROXA features (breakpoints, map local, repeat, etc.) work with simulator traffic