This guide was created with Scribe in 2 minutes. Sign in and create your own!
Android Example - Troubleshooting Errors in Sentry - Ecommerce App
Jay Revels |
0 step |
2 minutes
**App Error. End user experiences a failed checkout. End user submits feedback about not being happy.**
Zoom Saved
2
**Slack notifies the development team checkout failed error**
Zoom Saved
3
**Sentry provides the "Who", "What", "When", and "Why" clues on the root cause of this issue**
Zoom Saved
4
**See a screenshot of what the user saw at the time of the crash**
Zoom Saved
5
**Sentry provides an easily readable stack trace - It shows an unminified version of the stack trace.**
Zoom Saved
6
**To compare, Sentry provides the minified version, the raw stack trace, if you need it. Debugging with this view is not fun.**
Zoom Saved
7
**Sentry integrates with Github, click and find the problem code directly in Github.**
Zoom Saved
8
**One click brings you directly into Github - no need to login**
Zoom Saved
9
**The exact line of code is of course very helpful, but Sentry adds even more context to support the developer. Breadcrumbs - the timeline of activity that led up to this error.**
Zoom Saved
10
**Sentry provides a suggestion powered by AI**
Zoom Saved
11
**The suggestion tells us there is a problem with a function that is related to the backend.**
Zoom Saved
12
**Sentry also provides an insight into who might be the best person to solve this issue. Sentry pulls from the "Git Blame" API to retrieve who might be the best member to fix the issue**
Zoom Saved
Was this Scribe helpful? Save this document for future reference.
Save for Later
Have something to say?Create an account to leave messages for the author to see!Create an account
Feedback
This Scribe is in tip-top shape!Leave feedback if there are any issues with this Scribe