Get help with BugScreen
Most answers are below. If yours isn’t, email us — a human reads every message.
Using the BugScreen app
The app testers install to report bugs in an app that has no BugScreen SDK in it. The full walkthrough is in the companion app guide.
I don’t have a pairing code
Pairing codes come from whoever set up testing on your team — usually a QA lead or an admin. BugScreen can’t issue one for you. If you’re the person setting BugScreen up, create an app in the BugScreen console and the pairing code is on the app’s page.
My pairing code doesn’t work any more
Pairing codes can be rotated or removed, and a dead one deliberately gives no reason. Ask whoever sent it for a fresh one — devices that already paired are unaffected.
The app says it isn’t ready
You’re paired, but the app you’re reporting against has no issue tracker connected yet, so a report would have nowhere to land. An admin connects one in the BugScreen console. Nothing needs re-pairing afterwards.
I shared a screenshot and nothing happened
Check that you shared it to BugScreen and that the report form appeared. If it did and submitting failed, the most common causes are the app having no tracker connected (above) or the organisation having used its monthly report allowance.
Where did my report go?
Straight into your team’s issue tracker — GitHub, Jira, ClickUp or Slack. BugScreen forwards the report and keeps no record of it afterwards, so we can’t look one up for you — your team is who to ask. Screenshots are the exception: they’re stored for 30 days so the ticket’s image link keeps working, then deleted.
How do I unpair my device?
Open the cog on the app’s home screen and choose Disconnect. Re-pairing afterwards needs a fresh pairing code, because the app keeps no copy of the one it used.
Email us
Anything else, write to [email protected]. We answer by email, as quickly as we can.
Privacy and terms
What BugScreen collects, how long it keeps it, and the terms it is provided under are set out in our Privacy Policy and Terms.