Troubleshooting

No issues show up

• Check the DSN. It is shown once, when the key is made. If you’re unsure it’s the right one, create a new key, use it, and revoke the old one.
• Was the key revoked? A revoked key stops its SDKs at once. Open the app in Apps to see its keys.
• Is reporting on? setEnabled(false) holds across launches, and with requireConsent: true nothing is captured until grantConsent().
• Android: the app needs the INTERNET permission.
• Offline: reports wait on the device (at most 50, for up to 7 days) and are sent when the app comes back to the foreground.

A crash shows late

Crashes are sent on the app’s next launch. On iOS, signals and watchdog kills come from the system’s crash reports, which iOS delivers on a later launch.

A native crash has no stack

Android’s NDK crashes and ANRs come from the system’s exit records (Android 11 and later), which carry no stack. Each groups as one issue per kind (NativeCrash, ApplicationNotResponding).

Unrelated errors land in one issue, or one bug in many

Issues group by the frames in your own code. Set inAppPackages to your app’s own packages, so their frames, not a library’s, decide the group.

The same error is counted once

The SDK counts the same error more than 10 times a minute once, on the device, so a loop can’t flood your quota.

Errors stopped arriving at the end of the month

Your plan’s cap was reached. Usage shows what was dropped; the count starts again next month.

Sending to a tracker fails

The tracker’s keys aren’t set yet: set them in Settings → Issue tracker. A send that fails is tried again by itself; the issue’s Tracker panel shows each try and why the last one failed.