Make a first capture
Use one authorized device and a request you can recognize.
Where does your app run?
Start with one action you can recognize: refresh a catalog, load a poster, or switch audio tracks. JoesProxy runs on your Mac; the app making the request can run somewhere else. Choose that app’s platform below. You don’t need an agent, a command-line client, or a certificate just to begin looking for a connection.
Before changing settings, note the target’s current proxy configuration so you can put it back. Open Guided Setup on the Mac, choose the target and start capture. Use the address and port shown for this session; on a physical device, “localhost” means the device itself.
| Target | First investigation |
|---|---|
| Mac app | Refresh a catalog and follow its request from the session table to the response inspector. |
| Xcode Simulator | Open the verification page on one booted simulator, then distinguish the app’s own refresh from the browser check. |
| Physical iPhone or iPad | Connect over Wi-Fi and use the verification watch to pick one phone’s request out of the Mac’s traffic. |
| Apple TV | Switch audio tracks on a test title and compare what the player requested with what you heard. |
Want help from an agent or the terminal?
These are ways to work with JoesProxy on the Mac, not alternative ways to route a device. Connect an MCP client to ask which setup step still needs a person. Or start with the CLI to read the setup guide offline, then check a live connection separately.
How do I know setup worked?
The first useful result is one request you can tie to one action. If you only see a tunnel, you’ve established routing, not access to the response contents. If you can inspect the response, you still need to check what the app did with it. Use the setup checkpoints to decide what to test next and when to stop.