Manifest Chess Lite bug reports and feature requests on GitHub

Tell us what broke

Every bug, crash, and feature request for Manifest Chess Lite is tracked in the open on GitHub. Anyone can read it. Filing takes a free GitHub account and a few details that make the problem reproducible.

Crashes, a game that will not open, a move that reads wrong, a theme that looks off, and anything you wish the app did instead. All of it belongs here, where it stays visible and you can follow what happens to it.

Search before you file. If your problem is already on the tracker, adding your version and your steps to that thread is worth more than opening a second one.

Bug reports, crash reports, and PGN files

How to file an issue we can act on

Most bugs live or die on one thing: whether someone else can make them happen again. These six habits are what turn a report into a fix.

  1. 1

    Search the tracker first

    Look through the open issues and the closed ones. A closed issue often already carries the answer, and adding what you are seeing to an open thread helps more than a second copy of it.

  2. 2

    One problem per issue

    Two bugs in one thread means one of them gets lost. File them separately, and link them to each other if they are related.

  3. 3

    Say what you did, what you expected, and what happened

    Exact steps, in order, from opening the app to the moment it went wrong. This is the part that decides whether anyone else can reproduce it.

  4. 4

    Include your versions

    The app version is in the menu bar under Manifest Chess Lite, then About. Add your macOS version and which Mac you are on.

  5. 5

    Attach the PGN when the file is involved

    For anything about a game that will not open, a move that reads wrong, or a file that saves oddly, a small .pgn that shows the problem beats any description. Trim it down to the one game that fails.

  6. 6

    Show it if you can see it

    A screenshot or a short screen recording settles most questions about the board, the layout, or a theme.

Asking for a feature

Describe the problem before the solution. What were you trying to do, what got in the way, and what would have made it work? That makes the case on its own, and it leaves room for a better answer than the one you had in mind.

GitHub labels on the Manifest Chess Lite tracker

How issues get sorted

Labels go on once the issue has been read, so you do not need to pick one. If you are looking for somewhere to start contributing, good first issue and help wanted are the two to filter by.

  • bugSomething isn't working
  • enhancementNew feature or request
  • questionFurther information is requested
  • documentationImprovements or additions to documentation
  • accessibilityBarrier affecting people with disabilities
  • good first issueGood for newcomers
  • help wantedExtra attention is needed
Private, account, and purchase questions off the issue tracker

When to email instead

Everything on the tracker is public, and stays public. Some things belong in email for that reason alone.

Anything personal

Keep your email address, your order number, and anything else you would not post in public out of an issue. Send those to us directly.

Purchases, refunds, and your account

These need details that should not go on a public thread. Email us, or read the Complaints Policy for how a complaint is handled.

Security and privacy problems

Email us before filing anything public, so the problem can be looked at first.

Not sure it is a bug

Ask in the community at r/manifestchess, or just email and we will work out what it is.

No GitHub account, and you would rather not make one? Email hello@manifestchess.com and we will take it from there.

Manifest Chess Lite source code

Want to see the code behind the bug?

Manifest Chess Lite is open source under the GPL, and the complete source for the App Store build is on GitHub.