Grouping rules
A new error event is assigned to an Issue in this order:- If its fingerprint matches an existing Issue, it joins that Issue.
- If the fingerprint differs but the error is similar, it joins the most similar Issue. Similarity is compared only among Issues at the same error location.
- If no Issue is similar, Flashduty creates a new Issue.
RenderProcessGone, ChildProcessGone), NDK crashes from Flutter and React Native apps, and a located iOS App Hang, HarmonyOS freeze or jank, or Android ANR are grouped by fingerprint only, without the similarity step. Their error messages are almost identical, so similarity grouping would merge crashes from different locations into one Issue.
Default fingerprint
When an error event doesn’t carry a fingerprint, Flashduty calculates one from the attributes below. To set up the Web SDK, see Web SDK integration.Error location
The same error message can be thrown from unrelated places. Grouping by message alone puts everyCannot read properties of undefined (reading 'id') in an app into one Issue. Flashduty therefore also counts the error location in the fingerprint.
The location keeps only what survives a rebuild: no line or column numbers, no build hashes, and no minified or obfuscated short names.
A frame of app code without a symbol differs by its offset into the image, which is stable within a single build only, so the same iOS crash can become a new Issue after every release.
Handled errors on iOS take no error location: their message usually names the cause, and leaving the location out keeps existing Issues receiving them. Neither do Android NDK native crashes; they already group by the topmost application native frame. An error with no stable location, such as an Android exception with only obfuscated frames, keeps grouping by type and message alone, and is compared by similarity only with Issues that also have no error location.
An Android ANR’s message is always
Application Not Responding, and a HarmonyOS freeze or jank’s message is a constant too, so only the error location tells them apart: a located ANR, freeze or jank gets its own Issue by location and skips the similarity step.
Custom fingerprint
If default grouping doesn’t meet your needs, you can fully control error grouping behavior by providing a custom fingerprint.- Manually Add Fingerprint
- Use beforeSend Callback
When manually reporting errors, add a custom fingerprint through
addError:- Custom fingerprint must be a string type
- Errors with the same fingerprint within the same service will be grouped into the same Issue
- Errors from different services will be grouped into different Issues even if they have the same fingerprint
- Use the
beforeSendcallback to filter irrelevant errors; see “Third-party script error filtering” below
Web-specific considerations
SourceMap Integration
SourceMap Integration
Upload
sourcemap files to decode minified stack traces, ensuring grouped error stacks can be mapped to original source code.Third-party Script Error Filtering
Third-party Script Error Filtering
The SDK doesn’t filter errors from browser extensions or third-party scripts automatically. To exclude them, configure
beforeSend:View grouping results
In the Flashduty platform, navigate to “Error Tracking” to view the grouped Issue list. Click the Issue count on an application card to open that application’s Issues for the last 24 hours with status “all”. The count matches the card. Each Issue contains:Next steps
Issue Status
Learn about Issue status transition mechanisms