Crash reports are not showing on dashboard
complete
Flip van den Bosch
Since last week, we are not getting any crash reports anymore. While we know we have crashes. We did update the mapping files for the version that is crashing. The last crashes are 8 days old. While we have a client that is crashing every 2 minutes now. So we don't see what is causing the problem.
Log In
Petra Gluhak
complete
Petra Gluhak
in progress
We're on it 🎉
M
Mrkva David
Flip van den Bosch
Hi Flip,
Are you observing this behaviour on multiple devices or is the single device ?
Do regular feedback reports arrive on the dashboard normally ?
Is crash report user alert turned on via flag "isAskForCrashDescriptionEnabled" ?
Assuming the mapping files are correct, and there is no missing dysms indicator for your app visible on your Shake Dashboard, the crashes should arrive after each launch after crash event.
Flip van den Bosch
Mrkva David: All our clients have this. No crashes are reported for the last 14 days. Yes we have isAskForCrashDescriptionEnabled on. Also it did work for weeks. And suddenly (i think after the last big update where you implemented the user) no crashes are sent anymore. I don’t think we did change anything in configuration. And if we did, its strange that also for old apps no crash report come anymore.
Regular feedback is coming fine.
M
Mrkva David
Flip van den Bosch:
Regular feedbacks coming through are an indication that something specific might be happening only to the "crash reports" on the server-side, as they use the same "flow" in code as regular feedbacks, so I will assume that reports are arriving server-side.
We'll pass this to our server team so they will take a look as soon as they can. If the crash reports are "leaving" the phone and arriving on the server the problem should be fairly straightforward to spot.
If we find that crash reports are not arriving at all but regular feedbacks are, this means that there is a bug in the SDK which causes this faulty behaviour, but as you mentioned, if the feature was working fine for weeks there must be some specific edge cases involved.
Thank you for the details around the issue, the team will try to reproduce this or find the bug, you'll be automatically notified if this happens.