Getting Started
Bug Reporting
Crash Reporting
Surveys
Sentiment Insights
Versions
Force Update
Mobile AppStacktrace
The stacktrace is primarily used by developers to identify the exact line of code and cause of a crash. By examining the function calls and the order in which they were made, developers can trace back to the source of the error and understand why it occurred, which is essential for effective debugging and fixing the issue.
Detailed Trace
The core of this page is the stacktrace itself, which shows a list of function calls in the order they were executed, leading up to the point where the crash occurred. If you have uploaded the mapping file in version control, it can translate obfuscated code back into readable form.
Trace Sequence
The stacktrace starts from the last function called (where the crash happened) and works backward through the sequence of calls, providing a clear path of execution.
