Better handling of mobile app crashes

[GregOReilly]

Is there a more effective way to manage and group mobile app crashes?

We have a customer using a suite of mobile apps, and while crash detection is working well, we're seeing many repeated problem reports for the same underlying crash. This leads to unnecessary duplication and noise in reporting.

Ideally, we'd like to identify crashes we've already seen and tag them accordingly — for example, with a flag like seenBefore=true — to help us prioritize new or unique issues more efficiently.

In settings we are limited with options:

[Patrick_H]

The New RUM experience will have better error/crash grouping in Error Inspector and also features to manage crashes are planned there.