A report did not become a GitHub issue

Someone sent a report, but no issue appeared on GitHub. Work down this list — the first one that matches is almost always the cause.

1. The GitHub App is not installed on that repo

This is the most common cause. Reports are accepted and stored, but Glitchgrab has no permission to open an issue.

Check: open Repos and find the repo's card. The chip at the top right says not installed instead of LIVE.

Fix: press install app in the banner at the top of Repos, pick the repo on GitHub, and press Install. Refresh Repos — the chip should read LIVE. See Connect your GitHub org.

If you see the message GitHub App not installed on this repo — reconnect in Connect Repo to grant access, that is this cause. There is no "Connect Repo" screen — install from the install app link instead.

Reports sent before the App was installed do not become issues retroactively. Ask the reporter to send it again, or file it yourself from Chat.

2. It was an automatic error that was already reported

Automatic error capture is de-duplicated so a crash loop cannot flood the repo:

• the same error on the same page within 24 hours is not filed again;
• while an issue for that error is open, nothing new is filed for 7 days.

Check: search your repo's open issues for the error message. It is usually there already.

This applies to automatic capture and glitchgrab/server only. A person pressing the report button is never silently de-duplicated.

3. The reporter said it was the same as an existing issue

When the assistant or the form finds a matching open issue and the reporter confirms Yes, same problem or Add to #N, their words are added as a comment on that issue — no new issue is opened.

Check: on Reports, the card shows duplicate. Open the linked issue on GitHub; their comment is at the bottom.

4. The report failed

Check: on Reports, the card shows failed with the reason on a line starting ↳.

Common reasons:

• the App was removed or lost access to the repo (see cause 1);
• GitHub was briefly unavailable.

Fix: fix the cause, then dismiss the card and have the report sent again. There is no retry button on the Reports page.

5. The token belongs to a different repo

One token is one repo. If your app uses a token generated for another repo, the issue opens there.

Check: on API Tokens, find the token by its name and look at the REPO column. Compare it with the repo you expected.

Fix: generate a token for the right repo and put it in your app (see Create an API token).

6. Nothing reached Glitchgrab at all

If the report is not on the Reports page either:

• Development build — automatic error capture is off while NODE_ENV is development. Use the report button, or captureError, to test.
• Server code — reportServerError must be awaited on serverless hosts, and does nothing in development unless enableInDevelopment: true. See Capture errors from your server.
• Token revoked or expired — the SDK fails silently by design. Check API Tokens.
• Ignored on purpose — an error matching the provider's ignoreErrors list is never sent.

Still stuck?

Press ⌘⇧G on any Glitchgrab page and describe what you checked. Include the repo name and roughly when the report was sent.