SimNet
SimNet lets you test how your iOS apps cope with bad networks, right in the iOS Simulator. It puts simulators into Airplane Mode or onto a slow, lossy network, shows you the traffic their apps send, and records their screens, all without touching your Mac's own connection. This page covers how to set up and use the App and how to reach us if something isn't working as expected. SimNet requires macOS 15 or later, and Xcode with the iOS simulators you want to use.
You only need to do steps 2 and 3 once. Your Mac's own connection is never affected, whatever you choose in SimNet.
| Condition | Download | Upload | Delay | Loss |
|---|---|---|---|---|
| Airplane Mode | Every new connection is refused | |||
| 100% Loss | Connections open, but no data ever arrives | |||
| Edge | 240 Kbps | 200 Kbps | 400 / 440 ms | 0% |
| 3G | 780 Kbps | 330 Kbps | 100 ms | 0% |
| Very Bad Network | 1 Mbps | 1 Mbps | 500 ms | 10% |
| DSL | 2 Mbps | 256 Kbps | 5 ms | 0% |
| LTE | 50 Mbps | 10 Mbps | 50 / 65 ms | 0% |
| Wi-Fi | 40 Mbps | 33 Mbps | 1 ms | 0% |
These presets approximate Apple's Network Link Conditioner. Delay is added in each direction. On UDP, including QUIC and HTTP/3, lost data is really dropped; on TCP, it shows up as stalls while the data is sent again.
Everything in the menu can also be done from Terminal, in scripts, or in CI. First link the command onto your PATH:
sudo mkdir -p /usr/local/bin sudo ln -sf /Applications/SimNet.app/Contents/MacOS/SimNet /usr/local/bin/simnet
Then, for example:
simnet profiles # list the conditions simnet on airplane # all simulators, all apps simnet on 3g --sim booted # only booted simulators simnet on edge --sim <UDID> --bundle com.me.App # one app on one simulator simnet on --down 500 --up 200 --delay 300 --loss 5 # custom simnet log on # start network logging simnet status simnet off
The command line and the menu bar app control the same extension, so you can use them together.
Does SimNet slow down or change my Mac's own network?
No. SimNet only acts on connections opened by iOS simulators. Safari, Mail,
Xcode, and everything else on your Mac keep their normal connection.
Is SimNet a VPN?
No. SimNet doesn't send your traffic to any server. Simulator connections it
slows down are relayed on your Mac itself, to the same servers the apps were
already contacting.
Is SimNet made by Apple?
No. SimNet is an independent App and is not affiliated with, endorsed by, or
sponsored by Apple Inc.
The switch in SimNet's menu is grayed out.
SimNet's network extension hasn't been allowed yet. Open System Settings >
General > Login Items & Extensions > Network Extensions, and turn on
SimNet Proxy. If SimNet asks you to restart your Mac to finish installing the
extension, restart it and open SimNet again.
I turned SimNet on, but my app still loads normally.
Check that the simulator is selected under Simulators, or that All simulators
is checked. If you entered bundle IDs under Only these apps, check that your
app's bundle ID is among them; the Recently affected list in the menu shows
the exact IDs SimNet has seen. If your app talks to a server on your Mac
(localhost), check Also affect localhost connections.
In Airplane Mode, my app's reachability check still says it's online.
That's expected. The simulator shares your Mac's network, so
NWPathMonitor and SCNetworkReachability still
report a network. Only the connections themselves fail or slow down. In
Airplane Mode, URLSession reports "Could not connect to the server"
(NSURLErrorCannotConnectToHost, -1004) rather than the
"not connected to the internet" error you'd see on a device.
An app that uses NWConnection doesn't recover after I turn Airplane Mode off.
A refused NWConnection waits for a network change that never
comes in the Simulator, so it stays in its waiting state until the app calls
restart(). URLSession and Safari recover on their own.
Why aren't DNS lookups affected?
Every app in a simulator shares one DNS resolver, and refused or lost lookups
can leave it stuck even after SimNet is switched off. So lookups always
succeed, and SimNet acts on the connections that follow them.
HTTPS requests show as "not decrypted."
That host's certificate couldn't be verified by your Mac, or the host needs a
client certificate, or the app pins its certificate. The first connection to
it fails, and later connections to that host pass through untouched, so your
app's retry works. Connections that were already open when you turned
logging on appear once the app reconnects.
Why does my app use HTTP/2 instead of HTTP/3 while logging?
SimNet blocks QUIC (HTTP/3) while logging, so apps fall back to HTTP/2 or
HTTP/1.1, which it can show you.
A simulator I booted after turning logging on isn't decrypting HTTPS.
SimNet installs its certificate into newly booted simulators while the menu
bar app is running. If you only use the command line, run
simnet log on again.
How do I remove SimNet's certificate from a simulator?
The certificate does nothing while SimNet isn't logging. To remove it, erase
the simulator, or run xcrun simctl keychain <udid> reset.
That also removes the simulator's saved logins and any other certificates
you've added to it.
SimNet asks for my Developer folder.
The first time you use Open App Data or record a simulator, SimNet asks you
to choose ~/Library/Developer, where Xcode keeps the simulators. Choose that
folder in the panel that opens. SimNet remembers it from then on.
My recording doesn't show touches.
Touches aren't drawn while Simulator is in full screen. Check also that Show
touches is on in Settings.
Which format should I save recordings in?
MP4 (H.264), the default, plays everywhere, including every browser, Windows,
and Slack. MP4 (HEVC) is smaller, but Windows needs a paid add-on to play it,
and some browsers can't.
Does SimNet collect any of my data?
No. SimNet doesn't require an account and doesn't collect, track, or share
any personal information. The network log and your recordings stay on your
Mac. See our Privacy Policy for details.
Have a question, found a bug, or have a feature request? Email us at contact@port21.com. Please include your macOS and Xcode versions, the iOS version of the simulator, and a short description of what you're seeing, and we'll get back to you as soon as we can.