Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rockxy.io/llms.txt

Use this file to discover all available pages before exploring further.

​
iOS Simulator Setup

Rockxy can inspect iOS Simulator traffic, but simulator setup still depends on certificate trust and app behavior inside the simulated environment.

​
What usually works well

  • the simulator shares the Mac’s broader network path,
  • Rockxy can still inspect the traffic once trust is correct,
  • the target app is easy to relaunch after a certificate or proxy change.

​
What you still need to do

Make sure:
  • Rockxy is running and capture is started,
  • the certificate is available to the simulator path,
  • the simulator trusts it,
  • the app is restarted after trust changes.

​
Good debugging loop

  1. launch the simulator,
  2. make the certificate/trust path complete,
  3. cold-launch the target app,
  4. trigger one HTTPS request,
  5. verify it appears in Rockxy.

​
Common issues

​
The app still shows SSL errors

The simulator likely does not trust the certificate yet, or the app cached a failed TLS state.

​
Some requests never appear

That can be a caching issue, a framework-specific network path, or traffic that never leaves the app because of local failure first.

​
The request appears but the body is not readable

That usually means the proxy path exists but HTTPS decryption is still not complete.

Mobile App Network Debugging

See the broader workflow for iOS and Android debugging.

Certificate and HTTPS Issues

Fix simulator TLS and trust problems.