Resolve, reopen, or mark User Feedback as spam, download Session Replays as rrweb JSON, and list a project's DSNs from the Sentry CLI.

View or explain several issues at once, see event attachments, and split WebAssembly debug data from the Sentry CLI. Older traces and large project lists no longer fail.

Agents using Sentry MCP now search each dataset with a dedicated tool, can see which events Sentry dropped and why, search logs with regular expressions, and open dashboards from a URL.

You can now filter and sort conversations in Explore > Agents on totals like cost, token count, tool calls, and errors.

The React Native SDK now records the calls, duration, and errors of native modules, and adds the active call to crash reports.

The Android SDK can now instrument Nav3 back stacks to capture navigation transactions, breadcrumbs, screen names, and more.

The Rust SDK can now report native crashes, such as segfaults in unsafe code, to Sentry.

Sentry Logs search now supports regular expressions (regex), so that you can search log lines that match a pattern, not just by the exact text.

The JavaScript SDKs now trace more AI frameworks, providers, and classifiers across Node.js, Bun, Cloudflare, and Deno, with more consistent data in traces.

The Android SDK can now report process deaths caused by Android 17's Memory Limiter as fatal Sentry events.

A key metric in your mobile application's health is app start time. We've introduced a new view, called App Starts, that leverages the automatic instrumentation in the Android and iOS SDKs to highlight specific changes in your app start spans between releases. You can now easily monitor your app start performance, and drill-down into a screen's start up time all the way down to events and profiles for span operations causing slowdowns.

Navigating between issues within a single trace is easier than ever with the new trace timeline. The trace timeline displays up to 100 other issues within the current event’s trace flattened into a timeline of events. You can navigate to all related errors and spans in the trace by clicking “View Full Trace."

Replays have always been a crucial part of the debugging workflow, but required leaving the issue in order to do so. Now embedded directly within the issue details page, Replay clips offer a way to save you precious time and context switching.

Cron monitors can now be managed in bulk.

You can now use is:unresolved directly in metric alerts which automatically excludes events from archived or resolved issues..

When you open a pull request in GitHub, Sentry will comment and inform you if there are any unhandled issues being caused by the functions you are modifying...

Stack trace links to source code and Codecov reports are incredibly useful features for developers. However, they previously required source context to be available. We now support stack trace linking for frames that lack context. These changes primarily benefit iOS, .NET, Android, and Native SDK users.

The "Open this line in GitHub" link will appear directly in the frame title as seen in this example. Other stack trace frames that do provide context, e.g. python, will also find their links in the same location.

Identify signs of user frustration with rage click issues in Sentry - a series of rapid clicks on an the same unresponsive element.

We're excited to announce canvas support is now available in beta for Session Replay videos. For all websites/apps that leverage HTML canvas elements, you...

We are excited to announce the continued rollout of backpressure management to more Sentry SDKs. Now available on Python > v1.30.0 , Java >v7.1.0 , and Ruby...