Issue
My application includes third-party frames that Sentry cannot symbolicate because I do not have the debug information files for them. These frames appear at the top of the stack trace (toward the crash) and show as Unknown in the Sentry UI. I want Sentry to ignore these unsymbolicated frames when grouping issues so that unrelated errors are not grouped together.
Applies To
All SaaS Customers and Self-Hosted Users
Any SDK that uploads debug information files for symbolication (for example, the Native, Apple, Android NDK, .NET, Unity, and Unreal Engine SDKs)
Issue Grouping / Stack Trace Rules
Resolution
Use stack trace rules (previously called grouping enhancements) to remove the unsymbolicated frames from grouping. Configure them per project in Settings > Projects > [project] > Issue Grouping, under Stack Trace Rules.
Stack Trace Rules differ from Inbound Filters in that they are specifically designed to manage the in-app status and grouping of stack frames. Unlike Inbound Filters, which are message-based and do not apply to minidumps, Stack Trace Rules provide precise control over how stack frames are treated, making them essential for handling minidump-based events.
Unsymbolicated frames have no resolved function name, so Sentry represents them internally with the value <unknown>. Add a rule that removes any frame with that function value from grouping:
stack.function:"<unknown>" -group
This rule matches every frame whose function could not be resolved and marks it as not contributing to grouping, so only your symbolicated frames are used to group issues. Caret (^) actions apply only to frames above the matched frame. To exclude the boundary frame itself, you must include both the base action and the caret action in your rule. The -app action marks the matched frame as non-app, while ^-app marks all frames above the matched frame as non-app. Similarly, the -group action removes the matched frame from grouping, and ^-group removes all frames above the matched frame from grouping. To exclude a boundary frame and all frames above it, use both the base (-app, -group) and caret (^-app, ^-group) actions together.
Stack trace rules apply to new events going forward and do not retroactively regroup existing issues. For matcher and action syntax, see the stack trace rules documentation.
Verification Steps
After updating your Stack Trace Rules, verify their effectiveness by:
Sending a fresh minidump or event.
Confirming that the plumbing frames are marked as non-app.
Checking the Event Grouping Information to ensure the frames are omitted from grouping.
Ensuring the issue title is derived from the top in-app application frame.