Record what you were doing and when the app quit before reopening it. Those two details help distinguish the incident from a later report about a helper or a second crash after launch.
Open Console and look under Crash Reports. Apple's guide to viewing reports describes the category and the .ips extension. Open the report nearest your note and read the process information first. If the name differs from the app, check whether it is a helper involved in the action you tried.
Match a report to the incident
Here is a shortened fictional example. Console and raw files can show the same information with different labels.
Process: ExampleEditor [1842]
Version: 4.2 (118)
Date/Time: 2026-11-18 09:42:17 +0800
Exception Type: EXC_BAD_ACCESS
Triggered by Thread: 7
The fictional editor's visible release is 4.2 and its build is 118. Send both numbers so support can identify the build that failed. Match the time, including the zone if present, with your record of the failure. Read the exception line next. Apple's description of crash report fields explains the header, exception and thread information. An exception type gives the circumstances of the termination. Use it alongside the failing action and sample input, since different bugs can produce the same exception type.
Look at the frames for the thread the report names, if one is identified. Copy only enough context to help someone locate the failure. For example, the top frames may show a helper's name, while the steps leading up to the failure tell support which input and menu action to use.
If you can reproduce the crash with a disposable example, compare the process name and version against the first incident. Keep the two timestamps, and note whether both runs faulted after the same operation. Recurrence with a tiny test file can give the vendor a file you can actually share.
Write a report someone can reproduce
Include the app version and build, macOS version shown in the report, what you tried, and whether the failure also happens on a small sample. In the hypothetical editor case, write down that the crash happened after opening a TIFF and selecting a particular export option. Record whether the same action works with a blank file. Record the exact export option so someone can try the same settings and input.
Save the original privately. Before attaching a copy publicly, scan paths, account names, file names and device identifiers in the body and any appended information. Replace sensitive detail consistently in the public excerpt. For a vendor's authenticated support inbox, follow the vendor's request for full logs only after checking what those logs contain. Keeping the original intact gives you more context if the support team asks for a specific field later.
Find the report that matches the action
Write the local time of the crash and the last step you completed. A program can stop once and produce a second report after it relaunches. A helper may stop around the same time. Compare the timestamp, process and app build in each report before choosing which one to send. Give support the time zone when it appears. Two reports from different devices can otherwise seem to describe the same event even when they happened hours apart.
For the fictional TIFF export, check whether the process is the editor and the build is the one you actually opened. A copy from another application folder may be an older version with nearly the same name. Use the About window when you can open it, and compare it with the report header. If the report describes a helper, note how it connects to exporting and include the editor's version as separate context. Keep the original file so an analyst can ask for a field you did not reproduce in the excerpt.
Read the exception description as one piece of evidence. In the example, the named thread identifies where to start looking, while the error name does not tell you which particular user action caused it. Keep the time and reproduction steps alongside the small section you share. If the crash occurs only after a particular file or plug-in is used, say that explicitly. A plugin name in a stack gives the vendor a place to investigate.
Reproduce with a sample that can be shared
If the failure is safe to reproduce, make a test copy or a new fixture with invented content. Cover the exact app menus and file type involved. Try the same action from a blank document and compare the result. A crash only with the original file may point support toward the input, format or metadata. A crash even with a simple new file can help them focus on the application, plug-in or environment. Record the results of both attempts.
| Record to send | Example from the fictional case |
|---|---|
| App release and build | ExampleEditor 4.2, build 118 |
| Exact incident time | 09:42:17, with the zone recorded in the report |
| Reproduction | Open the sample TIFF and select the named export preset |
| Comparison | Try the same preset with a blank file and record whether it quits |
| Diagnostic fields | Process, exception type and thread identifier when present |
Give the vendor the tested app and OS versions and any safe fixture that reliably produces the issue. Include a small explanation of what you expected to happen. If the app slows down without quitting, use the Mac workload check for elapsed time and Activity Monitor observations. Keep a note of old and new app behavior if an update changed the result.
When a failure has happened more than once, compare whether it follows the same operation. If the first failure occurred while opening a file and the second during import, put both in your observation log under distinct actions. Identify the good run too. A second machine that can open the sample may have a different build or plug-in. Note the difference before asking the vendor to draw conclusions.
Prepare a public excerpt and a private support copy separately
Before posting a log publicly, read it as plain text. Look at full paths, arguments, filenames and linked information. A location under your home directory can reveal account or project names. Replace private details consistently in a shared excerpt while leaving technical names that matter, such as the app build or exception. Give support the minimal information needed to reproduce your report. If the authenticated support service requests the complete file, check its contents and the intended recipient before sharing it.
Preserve the unedited report somewhere appropriately protected. If another incident happens, compare its time and sequence of steps. Attach the report for the incident you describe. If a suggested fix changes the export, use the same harmless sample to determine whether the failure is gone.


