Reporting Bugs - ATAC-Helicopter/VaultSync GitHub Wiki

Reporting bugs

Thanks for helping improve VaultSync. Good bug reports make fixes faster.

Before you file

  • Make sure you are on the latest version for your channel.
  • Try to reproduce the issue after a restart.
  • Check Troubleshooting.md for common fixes.

Where to report

Use GitHub Issues:

What to include

  • VaultSync version (from the footer or tray header).
  • Operating system and build.
  • Steps to reproduce.
  • Expected result vs actual result.
  • Screenshots or short screen recordings if UI-related.
  • Relevant logs (see below).

Logs and diagnostics

  • If the issue is backup-related, include the recent backup log output.
  • If it is update-related, include update banner text, current version, target version, and any patch-preflight diagnostics.
  • Prefer exporting a support bundle from Settings > Advanced when possible. Review its exact file list first; remove optional sanitized diagnostics or anonymized telemetry if they are unnecessary. VaultSync pseudonymizes known paths and display identities, scrubs configured and structured secrets, limits file and bundle sizes, and includes a checksum manifest. It never sends the ZIP automatically, so inspect it again before sharing it.
  • After a crash, VaultSync can prepare a strictly redacted local report for you to inspect and email manually. It never sends the report automatically; see Crash reporting and user control for the exact fields and privacy controls.

Security issues

If you believe you found a security issue, avoid public disclosure and follow the security policy.