We've revamped the local variables UI in the stack trace view to make debugging a breeze!
Sentry Performance officially supports INP (Interaction to Next Paint) - Google's newest core web vital.
With Sentry React Native SDK 5.16.0 and Expo SDK 50, it’s now easier than ever to use Sentry with Expo applications.
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.
