LaunchTrace Support
A few checks solve most tracing questions.
LaunchTrace does not show anything useful
Make sure you selected the app you actually want to trace and started a fresh session. The Actionable view intentionally suppresses large amounts of routine macOS framework noise. Switch to Raw Log if you need to inspect the complete captured stream.
The target app was already running
Turn on Fresh Launch when you want LaunchTrace to terminate an existing instance first and capture a clean launch from the beginning.
I expected an early launch message but do not see it
LaunchTrace arms capture before starting the target app, but some messages may still be categorized as routine noise. Check Raw Log and use search when you need to verify whether a specific message was captured.
A warning appears only in Raw Log
That can be normal. LaunchTrace keeps routine Apple subsystem chatter out of Actionable view unless it matches a diagnostic class such as an application-authored warning, file problem, permission problem, error or crash.
The app crashes during a trace
LaunchTrace is designed to keep the session and surface crash-related diagnostics so you can inspect what happened immediately before termination.
I want to share the result
Use Copy Event for one diagnostic or Copy Summary for a compact representation of the launch session.
Need the normal workflow?
The LaunchTrace User Guide covers choosing an app, starting a trace, Actionable view, Raw Log, Fresh Launch, recent sessions, and copying evidence.
Need direct help?
Email support@tomglanderdigital.com. Include your macOS version, the app you were tracing, what you expected to happen, and a screenshot when useful.