Skip to main content
Use Strawberry -> Report Issue from the application menu to send an issue report. The message field is optional, but a useful report helps the team diagnose faster.

​
What gets shared

Submitting an issue report sends app logs and a diagnostics bundle to Strawberry support. Depending on the problem, it can include recent logs, app and device details, open-page information, and performance, file-sync, or other troubleshooting details. When available, Include chat and Include a screenshot of this tab are selected by default. Turn either off if you do not want to include it. Files you attach are sent too. Review those choices and attachments before submitting. Logs help diagnose crashes, failed integrations, update problems, migration issues, transcription problems, and browser errors.

​
What to include

Add:
  • What you were trying to do
  • What happened instead
  • The route or page you were on
  • Whether the issue repeats
  • The relevant connected app
  • The time the issue happened
  • Any visible error message

​
Billing or account issues

For billing issues, include:
  • Account email
  • Plan or team involved
  • Whether it happened in personal billing or team billing
  • Stripe portal behavior if relevant
  • What action you took, such as upgrade, downgrade, cancel, top-up, add card, invite, or seat change

​
Privacy note

Do not paste secrets, passwords, private customer data, or sensitive tokens into the issue message.

​
Before reporting

If Strawberry is still running and the issue is not an unexpected exit, try:
  1. Restart Strawberry.
  2. Reproduce the issue once.
  3. Report immediately after reproducing so logs contain the relevant event.

​
If Strawberry will not open or keeps exiting

Download the Strawberry Diagnostics Collector for Windows or macOS. It runs separately and saves a local report without uploading anything. On Windows, open the collector before reopening Strawberry after an unexpected exit. Click Start and wait a few minutes. It saves existing crash reports first, then automatically observes a running Strawberry or opens the installed copy to capture startup. You do not need to close Strawberry; the collector finishes on its own and leaves it running. If Strawberry cannot start or exits during collection, the report still includes the available evidence and any launch error. Drag the finished report into your private support conversation, or click Show in File Explorer. No setup or mode selection is needed. Technical details are available if support needs them. Review the report before sharing it. Logs and crash dumps can contain private information, including page contents or tokens held in memory. Include the incident’s local time and what happened in your message. Support can help with longer monitoring or additional crash and hang capture if needed.