Send Diagnostic Report

If you think something is not working correctly, and you'd like to bring it to the attention of the QRecall developers, please send a diagnostic report.

Sending a diagnostic report Steps

Choose Help ➤ Send Report… from the menu.
In the Comments field, describe your problem or question. The more details, the better.
Enter an optional reply e-mail address, especially if you expect an answer. If omitted, any responses will be sent to the e-mail address on record for your installed, permanent (or beta), identity key.
Click the Send button.

Feel free to follow up, via e-mail, with any additional information you think would be helpful. (Before you do that, see "What gets sent…" to see what information was already included in the diagnostic report.)

Sending a report requires an active Internet connection.

What gets sent… Details

A diagnostic report compiles the following information and then uploads it to the QRecall servers:

The comments you entered into the Comments field
A sampling of all QRecall processes running at the moment you send the report
Your most recent QRecall log records
Your QRecall preference settings
Your identity key's serial number (this lets us find you in our customer database)
A copy of your actions
Any diagnostic reports that have been created by the operating system for a crashed or hung QRecall process
An anonymous system profile
Key information about your installed QRecall components (launchd configuration files, and so on)

If you can read shell scripts and want to know exactly what gets included, you can review the QRecall.app/Contents/Resources/buildreport.sh script, inside the QRecall application bundle. This is the shell script that collects the report's information.