Mobile devs know the struggle. Small regressions can cause big issues in production, and fixing them isn't as easy as pushing a quick patch. Unlike a web app, shipping fixes for apps means navigating app store approvals, and often hopping on meetings with customers to debug because mobile issues can be so challenging to recreate. Catching these issues before the 1-star reviews roll in is crucial. Luckily, Sentry just made it easier than ever.

Which JS framework is the most performant? React, Vue, Svelte, Angular,…? When trying to answer this question, we often get lost in comparing benchmarks for reactivity, bundle size, memory usage and other factors. Of course we want to choose the best framework to create performant apps! But your app will only benefit from framework performance if you also follow best practices for performance optimization of web apps in general, and React apps in particular. So, where to start?

Bugs don’t announce themselves politely. They crash your checkout flow, break authentication, or slow your API to a crawl—usually right before your CEO asks how things are going. And when the error inbox is flooded with a hundred variations of TypeError: cannot read property of undefined, figuring out what actually matters can feel impossible.

Even at Sentry, we're not immune to downtime. In a moment of "oh-the-irony," we once took down our own application with a bad migration. We were adding a field to a critical database table, and the migration locked it completely. Since this table was essential to Sentry’s operation, the entire app went down. The website wouldn’t load, ingestion paused—everything ground to a halt.

This guide explains how errors work in PHP and how to debug them efficiently using logging functions and Sentry. The information in this guide is correct for PHP 8 and perhaps above, depending on how much future PHP versions change.

Sentry uses Issue Grouping to aggregate identical errors and prevent duplicate issues from being created, and duplicate alerts being sent. One of the chief complaints we’ve heard from our users is that in some cases the existing algorithm did not sufficiently group similar errors together, and Sentry would create separate issues and alerts, causing unnecessary disruption–or at least annoyance–to developers.

We’ve all worked on that app that hangs just a little too long in weird places, or had that query we could never get to perform just right. The network waterfall in Chrome DevTools can’t quite show us what’s going on behind the scenes, and tracing with OTel (and honestly, tracing in Sentry) was just… hard. Today that changes.

Sentry integrates directly with the tools you already use, giving you real-time crash and performance insights for Unity, Unreal Engine, and Godot. No matter what engine you use, Sentry helps you find and fix issues before they impact your players.