How crash reporting works.
When something goes wrong, the app sends the error and a short log to Sentry. Most of the bugs worth fixing show up on hardware and firmware combinations nobody on the project owns, and this is how we find them. It is on from the first launch, and there is a switch in Settings. Here is what a report actually contains.
In the report
- Crashes, errors and app log lines
- App version, build, platform and OS version
- Flipper name, serial, BLE address and
device info
- A masked replay of the seconds before a failure (Android & iOS)
Not in the report
- Keys you have recovered, and card UIDs
- GPS coordinates, removed before the report leaves
- Archive file names, replaced by their extension
- Your IP address, which Sentry is told not to store
- Screenshots, account details or advertising IDs
To turn it off: Settings → Diagnostics → Share logs with developers. That calls Sentry.close(), so the SDK and its native handlers shut down: nothing is queued and nothing goes out later. The replay has a switch of its own.
The full telemetry notice