Getting help

A useful report explains the action you took, what you expected, and what happened instead. Start with the smallest example that reproduces the problem, using non-sensitive text or a disposable test item where possible.

Find your version

Open Settings → About. Record the version and build number shown there. Include whether you are running a released installer or a development/preview copy; update behavior and operating-system permissions can differ.

For an update problem, also record the message under Check updates. A copy that cannot update itself can say This copy of Nock doesn’t update itself. That state is different from an update-service outage.

Public downloads are still being prepared. If the official download page says Coming soon, report a broken page only if something else failed; the holding message itself is expected. See Availability.

Build a clear reproduction

Include:

• Your operating system, Nock version, and affected feature.
• The starting state, including the selected voice/model mode when relevant.
• The steps you took in order.
• The expected result and the actual result.
• The exact visible error and approximate time.
• Whether it happens every time, and whether it began after an update or settings change.

For dictation, say whether Nock heard words but failed to insert them, or produced no transcript at all. For sign-in, identify whether the browser failed to open, authentication failed, or the return to Nock stalled. For a connected app, include whether the action completed at the destination.

Screenshots and logs

Capture the relevant control and message. Crop unrelated windows and review visible account details. Never send provider keys, sign-in codes, callback URLs, session tokens, full payment details, or private project content in a public issue.

If asked for diagnostics, review them first and share only through the indicated support channel. Do not change or delete configuration files as a first troubleshooting step; that can remove evidence and saved state without solving the cause.

Revisit onboarding

Settings → About includes Replay tour and Replay intro. Use the tour to review the interface and first-run workflow. Replaying it does not guarantee that a denied system permission has been granted; check permissions separately.

Optional setup tips

Where the service is available, About offers setup tips by email. Entering an address alone is not enough: the interface requires the consent checkbox and an email confirmation. Stop emails and the unsubscribe link withdraw that choice.

Setup tips depend on Share usage data, because they respond to incomplete setup steps. Turning sharing off requests withdrawal from the tips too. If Nock cannot reach the service, that withdrawal is retried later; the email’s unsubscribe link is another way to withdraw. Tips are optional and are not a substitute for reporting a reproducible error.

Start with Troubleshooting, Sign-in troubleshooting, or Usage troubleshooting before collecting a larger report.