Preserve previous-session evidence
Choose between saving a recovery copy, reopening a recording, and making a new observation.
When the app offers previous-session recovery, decide whether you need a copy of the evidence or a restored workspace. Those operations are different from replaying requests.
Preserve before interpreting
- If previous-run evidence is offered, save a native recording copy before replacing your current working set. When available, the recovery export path can preserve a file from disk without first loading every response body into the inspector.
- Use a native recording for another JoesProxy investigation. Choose HAR for interoperability, not as a complete substitute for native state.
- Reopen your copy and inspect one known request: is the method and status present, did the capture retain the body you need, and does the inspector identify truncation or omission?
Understand the limits
Recovery depends on what was actually written. A gap can represent an unwritten request or unretained bytes; it is not evidence that no traffic occurred. Restoring captured sessions does not restart a listener, reactivate a mock or reconstruct the device state.
FAQ: can a larger save mode recover a missing body?
No. A new export cannot recreate bytes that were never retained. For a repeatable issue, make a fresh capture with the required retention settings and save a new recording. Keep the previous copy separate so it remains clear which evidence came from which run.
Finish
Keep only the copies you need, check exports for sensitive data, and verify the normal device route before resuming unrelated work. Do not deliberately crash the app to test this flow.
