Choose a capture target

Choose the least setup your question needs

“Did my app contact the service?” needs less access than “Which field did the service return?” Begin with a test account and an action you can repeat, such as refreshing a catalog. Write down the existing network configuration before changing it.

Is the listener available? Start capture on the Mac and note its displayed address and port. Other devices must be able to reach that Mac. A listening port alone says nothing about an app.
Did this app use it? Trigger one fresh action on your chosen Mac, Simulator, iPhone or iPad, or Apple TV. Match the time and host in the capture. For a tunnel you may only see the host, not the path. If no matching traffic appears, troubleshoot routing before installing a certificate.
Can I read the response? Only if needed, complete the platform guide’s trust steps for your authorized test, then repeat the action. Select the new request and look for its status and available response data. A downloaded profile doesn’t prove the target installed it.
Did the app behave as expected? Inspect the app itself. Record whether the list populated, the error appeared, or the audio resumed. A successful HTTP request can’t answer those questions.

Hand off a result someone can repeat

A useful handoff can be two sentences: “On the test iPad, I refreshed the catalog once. The matching response contained three items, but the list on screen stayed empty.” That gives the next investigator a starting point in the app. If you saw only a tunnel, write “I saw a connection to the catalog host; I couldn’t inspect the item list.” Those observations point to different next steps.

Record the target, the action, the matching request and what you saw in the app. If you only saw a tunnel, say so. Share the minimum necessary evidence rather than the entire session. Restore prior routing and temporary trust using the target’s walkthrough, then repeat the ordinary action with JoesProxy stopped. If a checkpoint failed, troubleshoot by symptom.