When receiving multiple similar reports, it would be very beneficial to have
them grouped.
One could do this by generating a signature by hashing various components of
the stack trace:
- The root exception class (ex: NullPointerException)
- The "interesting" class (ex: org.example.SomeClass)
- The line number of the "interesting" class
- The app version
The "interesting" class is defined as either (in prioritized order):
- The top class from the root that lies in same package as the application
- The class just below the top exception
Ideas about signatures can be found in:
https://github.com/ACRA/acralyzer/issues/2
http://support.hockeyapp.net/kb/about-general-faq/how-does-hockeyapp-group-crash
es
Original issue reported on code.google.com by kfo...@gmail.com on 13 Aug 2013 at 5:37
Original issue reported on code.google.com by
kfo...@gmail.com
on 13 Aug 2013 at 5:37