Skip to content

Report a bug or submit debug logs

Something not working right? You can report a problem to the Letro team from inside the app, and optionally attach debug logs to help them find the cause faster.

Security note: Debug logs describe how the app is behaving — things like errors, timings, and which screen you were on. They do not contain the decrypted content of your messages, calls, or files. To keep them safe, only ever send logs through Letro's official in-app Submit debug logs option — never email a log file or post it anywhere else.

What are debug logs?

Debug logs are a technical diary the app keeps about its own activity: connection attempts, sync events, and error messages. When you hit a bug, these logs let Letro's support team see what went wrong under the hood, even if it's hard to describe in words. Submitting them is optional, but it makes most bug reports much quicker to resolve.

On Web & Desktop

To report a problem:

  1. Click your avatar (top-left), then open Settings.
  2. Go to Help & About (or Feedback, depending on your build).
  3. Select Report a problem.
  4. Describe what happened — what you did, what you expected, and what actually occurred.
  5. Leave Send debug logs ticked if you want to include them, then click Send.

To check your app details before reporting:

  1. Open Settings → Help & About.
  2. Note your app version here — it's useful to include in your report.

On iOS

  1. Tap your avatar (top-left), then tap Settings.
  2. Tap Help & About.
  3. Tap Report a problem.
  4. Describe the issue in your own words.
  5. Keep Send debug logs enabled, then tap Send.
  6. To find your app version, stay on Help & About and read it near the top.

On Android

  1. Tap your avatar (top-left), then tap Settings.
  2. Tap Help & About.
  3. Tap Report a problem.
  4. Describe the issue in your own words.
  5. Keep Send debug logs enabled, then tap Send.
  6. To find your app version, stay on Help & About and read it near the top.

Good to know

  • Be specific. The date and time it happened, the silo or person involved, and the exact wording of any error all help the team reproduce the problem.
  • Reproduce it first if you can. If a bug is repeatable, trigger it right before you submit logs so the relevant activity is fresh in the log.
  • Logs are capped. The app only keeps recent activity, so report while the issue is still happening rather than days later.
  • The Help & About page also holds useful links (terms, privacy, and support resources) and your app version — handy to have open when you write your report.
  • Sending a report doesn't open a live chat. If you need a direct reply, use the support contact options instead.

Related: