Skip to main content

Send diagnostics

Sending a diagnostics file with your report makes the cause much faster to find. The file holds environment details and recent logs, and never content such as dictated text or translations.

Creating it​

  1. In Settings → General → Diagnostics, turn on Write debug log.
  2. Do the action that caused the problem once more.
  3. Press Export diagnostics in the same section.
  4. A file named Sogon-진단-<date>-<time>.txt appears on your desktop.
  5. Press Report an issue in the same section. A GitHub issue form opens with your app version, macOS version, and permission state already filled in. Drag the file from step 4 into that form.
  6. When you are done, turn Write debug log off again.

The issue and its attachments are public. Feel free to open the file first — what it does and does not contain is listed below.

Sogon records nothing that happened before you turned logging on, so reproduce the problem after turning it on.

What the file contains​

ContentsExamples
EnvironmentApp version, macOS version, Accessibility trust, whether the event tap is running, Secure Event Input state
Settings summaryShortcuts, recording mode, STT provider, overlay display
Recent logsShortcut triggers, permission states, transcription and correction stages, insertion results, restore failure reasons and character counts

What it never contains​

  • Transcriptions, corrected text, translations, copied text, snippet bodies
  • API keys and tokens. Anything that slips in is replaced with <redacted>.
  • The user name in home folder paths, replaced with ~
  • URL queries and fragments

Log files​

  • Location: ~/Library/Application Support/Sogon/Logs/. Open it with Open log folder.
  • The folder and files are readable only by your account.
  • When sogon.log reaches 5MB it rolls over to sogon.1.log once and starts fresh.
  • One event is one line, and a line never exceeds 2,000 characters.