Crash reports and feedback in FUTO Notes, and what they send
To report a bug or send a comment, open Settings → Send feedback, type your message, and press Send. Crash reports are separate: the app saves a report on your device when it crashes and asks on the next launch whether to send it. Both go to notes-crashlog.futo.org, need no account, and send nothing from your notes folder except what is listed below.
This page describes FUTO Notes 1.8.0 on desktop (Linux, macOS, Windows), iOS, and Android.
Send feedback from the app
- Open Settings and find the Issue reporting section.
- Choose Send feedback (“Report a bug, request a feature, or leave a comment”).
- Type your message. Add up to three screenshots with the photo button in the corner of the message box.
- Press Send. When it arrives, the app shows “Thanks. We’ll read it.”
The message can be up to 10,000 characters. There is no category to pick; every submission is read as a general comment. If sending fails, the form keeps your message so you can try again, and the text survives a restart. Attached screenshots do not, so add them again.
The feedback form works whether or not crash reports are turned on. Pressing Send is your consent for that one message.
What feedback sends
| Field | Desktop | iOS | Android |
|---|---|---|---|
| Your message | Yes | Yes | Yes |
| Screenshots you attached | Yes | Yes | Yes |
| App version | Yes | Yes | Yes |
| Platform | Yes | Yes | Yes |
| OS version | Inside the user-agent string | Yes | Yes |
| Device | The web view’s user-agent string and screen resolution | Hardware model | Manufacturer and model |
Feedback does not include a session ID, the screen you were on, the name of any note, or anything from your notes folder.
Screenshots
Each screenshot can be up to 5 MB. A PNG, JPEG, or WebP file under 5 MB is sent exactly as you picked it, including any metadata it carries, such as the location stored in a photo. Anything else, or anything larger, is re-encoded once as a JPEG at quality 95. If it is still over 5 MB after that, the app refuses it and tells you. Re-encoding applies only to feedback; images you insert into notes are never changed.
Report a bug in public
The public issue tracker is on GitHub at github.com/futo-org/futo-notes/issues. Use it if you want the report to be visible to others, or to follow a bug. Anything you post there is public, so leave out note contents you want to keep private. The source code is at gitlab.futo.org/futo-notes/futo-notes.
How crash reports work
- When the app crashes or hits an uncaught error, it writes a report to a hidden
.crashlogsfolder inside your notes folder. Nothing is sent at this point. - On the next launch, if Share crash reports is on, the app shows a Crash Report dialog. You can expand View report to read the error, add an optional note under “What were you doing?”, and tick Send crashes automatically.
- Send (on desktop, Send Report) uploads every saved report and deletes them from the device once the upload succeeds. If the upload fails, they stay saved and you are asked again next launch.
- Don’t Send deletes the saved reports and turns off Share crash reports. Turn it back on in Settings if you change your mind.
On desktop, the View report panel shows the error, stack trace, type, platform, and version of the first report. The full report sent to FUTO has the extra fields in the table below.
Crash report settings
Both switches are in Settings → Issue reporting:
- Share crash reports is on by default. With it on, you are asked after each crash. With it off, the app never asks and never sends. Reports are still saved in
.crashlogsso that turning it back on can offer them. - Send crashes automatically is off by default. With it on, saved reports are sent at the next launch without the dialog. It only works while Share crash reports is on.
Development builds never send crash reports or feedback to FUTO’s production server. See Build FUTO Notes from source.
What a crash report contains
| Field | Desktop | iOS | Android |
|---|---|---|---|
| Error message and stack trace | Yes | Yes | Yes |
| App version, platform, and report type | Yes | Yes | Yes |
| Time of the crash | Yes | Yes | Yes |
| Random session ID, new each launch | Yes, except for crashes in the Rust backend | Yes | Yes |
| Device | Web view user-agent string and screen resolution; for Rust backend crashes, only the OS and CPU architecture | Hardware model and iOS version | Manufacturer, model, and Android version |
| Screen you were on | Yes, see below | No | No |
| Your note from the dialog | If you typed one | If you typed one | If you typed one |
Note: On desktop, the “screen you were on” is the app’s internal route. When a note was open, that route contains the note’s name and the folder it is in. If a note’s name is private, press Don’t Send, or turn off Share crash reports before the next launch.
Crash reports do not collect note contents, your sync password, or your server URL. The error message or stack trace is whatever the failing code produced, so it can occasionally mention a file or folder path. The privacy policy covers how FUTO handles reports once they arrive.
Turn crash reporting off
Open Settings → Issue reporting and turn off Share crash reports. To also clear reports already saved on the device, delete the .crashlogs folder in your notes folder. See where your notes are stored to find it, and network requests FUTO Notes makes for everything else the app can send.
Next steps
- Network requests: every other request the app can make, and how to turn each off.
- Privacy policy: how FUTO handles reports and feedback once they arrive.
- Build FUTO Notes from source: development builds never send to FUTO’s server.