Help us help you. The more of the following you can include in a bug report, the faster we can reproduce and fix.

The bug-report template

Email support@screensolo.ai with:

  1. ScreenSolo version — ScreenSolo → About ScreenSolo on a Mac, Help → About ScreenSolo on Windows (e.g. 1.0.26)
  2. Operating system — e.g. macOS 14.4.1 (M2 Pro) or Windows 11 23H2
  3. iPhone / iPad model + iOS version (if AirPlay-related)
  4. Repro steps — what you clicked / connected / typed, in order
  5. Expected — what you thought would happen
  6. Actual — what actually happened
  7. Screenshot or video if the issue is visual

The pro move

If the bug is visible during a mirroring session, record it with ScreenSolo itself, then press ⌘E (Ctrl+E on Windows) and export it — the snapshots as a PDF (Guide → PDF, on Pro) or a short GIF of the moment it goes wrong — and email it to us. The screenshots plus your repro steps give us nearly everything we need in 60 seconds.

What we don't need

  • Crash dumps unless we ask — we have Sentry instrumentation that catches most crashes server-side
  • Logs unless we ask — they don't tell us much beyond the crash
  • A long preamble — straight to the repro is the fastest path to a fix

How long until we respond

  • Pro subscribers and Teams: 24-hour first-response SLA on weekdays.
  • Free: best-effort; usually within a week.
  • Outages / data-loss bugs: prioritised for everyone.

Public roadmap

We don't have a public bug-tracker yet (planned for Phase 2). Bugs you report become Linear tickets internally; when they're fixed the resolution lands in the Changelog.