We've shipped automatic code mapping and in-app frame detection for Java stack traces. Using our GitHub integration means Sentry can automatically link stack traces to your source code and figure out which frames belong to your application, improving stack trace readability and grouping quality – all without you needing to configure anything.
Quick Background
Previously, getting accurate stack traces, code links, and good grouping for Java often required manually setting up code mappings (linking Sentry to your repo) and in-app rules (telling Sentry which code is yours vs. a library). This was often skipped because it could be tedious, especially for projects with many packages.
How it works
If you've got the Sentry GitHub integration installed, here’s what happens automatically for your Java errors:
module: at.markushi.expensemanager.view.main.HomeActivity
abs_path: HomeActivity.java
It pieces together a potential file path like at/markushi/expensemanager/view/main/HomeActivity.java
It searches for that path in your connected GitHub repositories.
If it finds a unique match, Sentry automatically creates the code mapping and an in-app rule for that code path. This means future errors from the same code parts will be correctly linked and marked as in-app.
What You Get
Getting started
Note: If you've already set up manual code mappings, those will still take precedence.