Support & bug reports

Digr is an alpha, so bug reports are the most useful thing anyone can send. Here is where they go and what makes one actionable.

Report a bug

Open an issue on the public releases repository: github.com/BuildBeast/digr-releases/issues/new . Existing reports are at the issue list.

That repository holds Digr's downloads and update manifest rather than its source, which is private. Its issue tracker is the public support channel for now, and it is the one place this site sends you to GitHub on purpose. There is no support email address yet, and inventing one would just be an inbox nobody reads — a proper support form, with an address behind it, is planned.

Export a diagnostics report first

Digr can describe its own failure better than a screenshot can. In the app:

  1. Open Settings.
  2. Find Diagnostics, under the app's data location.
  3. Press Export Diagnostics and choose where to save the file.
  4. Attach it to the issue.

The export is a redacted report covering cast, playback and library state plus recent log lines. It is written when you ask for it and sent nowhere on its own — see privacy. Read it before attaching if you'd like to; it is a plain text file.

What makes a report fixable

  • What you did, in the order you did it.
  • What happened, and what you expected instead.
  • The version — shown in Settings, and in the sidebar footer. Currently 0.1.0-alpha.3.
  • Your macOS version and Mac model. macOS 11 Big Sur or later · Apple silicon.
  • Where the music lives — internal disk, external drive, network share — and roughly how many tracks. A surprising number of library bugs are drive bugs.
  • The file, if one track is involved: its container (FLAC, ALAC, MP3…) and whether other files in the same folder work.
  • The diagnostics export.

Before you report

A few things that are known and documented rather than broken:

  • New files don't appear on their own. Digr doesn't watch the filesystem yet; rescan the folder. This is on the roadmap.
  • An OGG file won't play. Decoding is macOS's job, and OGG is the container it typically can't handle. Digr reports it on that track rather than skipping it.
  • A track stopped instead of skipping. That is deliberate. A file that won't load stops playback with a reason, so one bad file can't walk your whole library.
  • macOS says the app is damaged. Nothing is published for download yet precisely because of this — the build is not yet signed by Apple. If you have a build, you got it from a private channel; see the changelog.

Keeping track of releases

Everything about a release is published here rather than on GitHub. Each version is written up version by version on the changelog, what is being built next is on the roadmap, and the download appears on the home page the moment there is one. Longer-form writing about the product is on the blog.