Prepare a safe desktop problem report

Prepare a useful Dosya desktop bug ticket while controlling screenshot, diagnostics, recent-log filenames, body length, and sensitive data exposure.

Last reviewed

The desktop problem form sends an authenticated support ticket. Its screenshot and diagnostics start enabled, while the recent log is opt-in because it can disclose filenames from synced folders.

Four panels show opening Report a bug, writing a repeatable description, reviewing enabled Diagnostics, and deciding whether to include the filename-bearing recent log.
Describe the repeatable failure and review each evidence source before sending the account-bound support ticket. Open full-size screenshot.

Before you start

  • Sign in first; otherwise the dialog instructs you to sign in and reopen Help > Report a Problem….
  • Arrange the window so its visible content is safe before sending because the screenshot is captured at send time and has no preview.

Steps

  1. Open Help > Report a Problem… or press Cmd/Ctrl+Shift+B. The dialog title is Report a bug and it creates a support ticket tied to the account.
  2. In What went wrong? What did you expect instead?, provide the smallest repeatable sequence, expected behavior, actual behavior, and approximate time. Blank text keeps Send disabled.
  3. Review Attach a screenshot of this window, enabled by default. Hide unrelated names or content before sending; the image is captured only after Send is pressed.
  4. Inspect the enabled Diagnostics rows: App, System, Workspace, Page, Error reference, Error, and Sync appear when values exist. Untick Include when that context is unnecessary.
  5. Leave Include the recent log (last 200 lines) off unless support needs it. The reader takes at most 64 KiB from the end of the log, and those lines can contain synced filenames.
  6. Select Send. The user text plus optional log is limited to 9,500 characters; a screenshot over 4,500,000 bytes or a failed capture is skipped while the ticket still submits.
Desktop sync activity view used to gather only the timing and error evidence needed for a safe problem report.
Collect a minimal reproduction and relevant timing before opening the report form; avoid unrelated file details. Open full-size screenshot.

Expected result

Success shows Report sent, says replies go to the account email, and includes the first eight ticket-ID characters when available. Screenshot skipped explains whether capture failed or the image was too large.

On Could not send report, keep the dialog open, review the returned description, and retry later. Common home paths are redacted in diagnostics, but that filter does not promise removal of every secret from text, screenshots, or logs.

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.

    Check the outcome before you retry

    Use these shared checks when a task needs a second look.