Download on the App Store
Menu

Getting help

Reporting a bug well

The fastest way to get a bug fixed: report it from inside the game so your details are filled in, write steps someone else can follow, and add exactly what VoiceOver or another assistive technology did.

Checked against OutBrick 5.1.1 · October 8, 20262 min read

Report it from the game

  1. In OutBrick, open Settings (the gear on Home or the Journey).
  2. Scroll down and tap Report a bug. Safari opens a new bug report in the community.
  3. Sign in if asked, check the details already filled in, and describe what happened.
The foot of the Settings Game tab with a purple Report a bug button beside a blue Community button.
Report a bug sits next to Community in Settings.
What the game fills in for you
FieldExample
DeviceThe model, for example iPhone18,2
System version27.1
OutBrick version5.1.1 (68)
Assistive technologyVoiceOver, Switch Control, Larger Text or colour filters, when they are on
LevelYour current Journey level

Good to know

Nothing that identifies you is sent: no name, no Game Center or iCloud identity, no advertising identifier. iOS does not let apps detect Voice Control or Zoom, so tick those yourself if you use them.

Write steps someone else can follow

The team needs to make the bug happen on their own device. Number your steps from opening the game:

  • Steps: “1. Open level 214. 2. Slide the red long brick left. 3. Use Undo.”
  • What should happen: “The brick goes back to where it was.”
  • What happened: “The brick disappeared and the moves counter went up by two.”
  • Does it happen every time? After a restart? On another level?

Accessibility problems

  • Name the technology and its settings: VoiceOver (with your speech rate or Braille display if relevant), Voice Control, Switch Control (auto or manual scanning), Zoom, Larger Text size.
  • Quote exactly what VoiceOver said, or the command Voice Control did not understand.
  • Say where focus was before and after, which gesture or action you used, and which rotor was selected.
  • Post it in Accessibility if you prefer: the team reads it most closely.

Screenshots and recordings

  • Screenshot: press the side button and volume up together.
  • Screen recording: add Screen Recording in Control Center, start it, reproduce the bug, then stop it.
  • Crop out your name, email and anything personal, and describe the picture in its alt text.

After you post

The team sets a status on every bug report: New, Confirmed, Fixed, Released, Not a bug or Duplicate, sometimes with a note such as “Fixed in 5.1.1”. Watch the thread to get an email when it changes. For anything private, use the contact form.

Was this guide helpful?

  • Troubleshooting common problems

    Quick fixes for missing progress, purchases that did not arrive, lives that seem stuck, no sound, missing notifications, widgets, videos that will not load and VoiceOver focus problems.3 min read

  • Using the OutBrick Community

    Signing in, choosing the right category, starting a thread, formatting, marking a solution, following threads and email, translations, voting on ideas, and keeping your details private.3 min read

  • Accessibility in OutBrick: start here

    Every way OutBrick adapts to you, from VoiceOver and Switch Control to colour-blind symbols, a high-contrast board, slower animation and no timers, with a starting point for your needs.5 min read

  • Playing with VoiceOver

    How the board reads, how to slide and swap with actions, the rotors, every gesture, what you hear after a move and how to get a free hint.7 min read

A person on the team reads every message. We aim to reply within two working days.

Still stuck?

Still stuck?

Ask in the community. The team and other players answer in the open, and your email address is never shown.

Ask the community

Found a bug?

A good report gets fixed faster. The bug form asks for exactly what we need.

Report a bug

Rather write privately?

The contact form reaches the same team, privately. Use it for purchases and anything personal.

Contact support