Capture from a Mac app

Use this flow when the app you are testing runs on the Mac. An iPhone on the same desk follows its own Wi-Fi settings; use the iPhone/iPad guide for that target.

Route one recognizable action

1. Note the active network service and its existing proxy configuration. If the settings are managed, check with its administrator before changing them.
2. Start the proxy listener in JoesProxy. Use the address and port displayed in Settings → Proxy, not a port copied from another test.
3. Enable system proxy routing for the active Mac network service. Check the routing indicator. A running listener and a routed service are different states.
4. Refresh a screen in your test app, such as a synthetic catalog. In Table or Explorer, find the host and path matching that action. If other Mac services appear, narrow the list by host and time.

When you need HTTPS contents

If host and timing answer your question, leave the connection tunneled. To read a response from a test service you’re authorized to inspect:

1. In the Mac setup walkthrough, check Create Root CA. If the expected test authority already exists, use it rather than creating another. Choose Install in Login Keychain if it isn’t installed.
2. Under Trust the Certificate, review the certificate and choose Trust Root CA. macOS may ask you to authorize the keychain change. Return to the guide and choose Refresh Status.
3. Select the intended host for inspection. Under Verify HTTPS Interception, choose Run Verify Test, then View in JoesProxy. This verifies the browser test. Repeat the action in your own app and select its new request before concluding the app can be inspected.

First investigation: why is the catalog empty?

Use a catalog in your own test app with a known item. Refresh once and select the new request in Table. If you can inspect the response, compare its status and item list with the screen: an empty list from the service is a different lead from a populated list the app didn’t display. If you see only a tunnel, don’t infer either result. Use Explorer and Table to see where to find the selected response.

Restore and verify

Stop capture, check that the previous service configuration is back, and remove any test certificate trust you added solely for this session. Trigger a fresh request with the listener stopped. If ordinary networking fails after an unexpected quit, restore the recorded settings for that service rather than resetting every interface.

FAQ: the browser appears, but my app does not

Check that the app actually made a new request after routing changed; a cached screen may not. Try one identifiable action in that app and look for its host without an old filter. Some clients do not honor system proxy preferences. More certificate trust will not fix missing routing.