Introducing Gearbox Crash Reporting //
Allow your customers to send you reproducible error reports when problems occur?
By using the Crash Reporting Gear, quickly solving your customers' problems becomes easy.
Why you need this Gear //
We all want our applications to run flawlessly, but in practise you have to prepare for problems. Whether problems are due to bugs or incorrect use of your software, you want to be able to quickly assist your clients. One of the most difficult things in remotely solving client problems is reproducing the problem locally.
If you can reproduce a problem, you have the key to solving it.
Nobody wants a 'it works for me' discussion with their clients or lengthy calls to understand the problem and the environment. Even when that leads to a reproducible use-case, it costs you and your client a lot of time and frustration.
How this Gear solves your problem //
The Crash Reporting Gear injects functionality into the application which allows tracking of user behaviour without slowing the application down. When a problem occurs, an error report can created manually or automatically (in case of a crash). The Crash Reporting Gear shows a popup that allows the user to give a description about what happened and send it to the developer. Different ways of sending the crash report can be defined, for instance by email or directly to a remote server.
When receiving a crash report, the report includes the information provided by the user, along with a stack trace (in case of a crash) and a limited history of user activity. This history can be used to accurately reproduce the user's actions leading up to the problem. Through the CrashReporting configuration, the application developer can define which (if any) context information is to be included in the activity history. Examples of context information are local component states or records the user is working on.