This is part 2 of a 3-part series on profiling. If you’re not yet familiar with the what profiling is, check out the first part in our series. By this point, you’re probably already convinced that good performance is important for your app’s success. There are many tools available for performance, but profiling in production with a modern profiling tool is one of the easiest and most effective ways to get a full understanding of your app’s performance.

Stack traces show us exactly where an exception occurred, but you can still be left wondering: What arguments or state caused the exception to occur? If you can reproduce the issue locally with a debugger attached you’ll have access to these local variables, but with Sentry you can identify the exception location without needing to reproduce the issue locally. By including local variables with stack traces, Sentry events become much closer to the full debugging experience.

We’re creating a new way to install and set up Sentry. Starting with Next.js, you’ll be able to set up new Sentry accounts or create new Sentry Next.js projects via the terminal and running a single command. Getting started is simple(r). While you can still visit sentry.io/signup to create an account or create a project from within the app – now you can skip all the clicks, navigate to your repo and run this command.

Bugs are one of the most troubling aspects of software development; they appear out of nowhere and cause everything to stop working. Most of the time, they can be resolved quickly; however, others can be gruesome and take hours/days to fix. Next.js is one of the most popular web development frameworks in the current world, and as a programming tool, it didn’t escape the bug dilemma either.

User experience and performance are two of the most important metrics of any game. You need to ensure that it runs as optimally as possible on any platform. Ideally, you don’t want to wait for players to angrily tell you something is not working or worse, broken. In a perfect world you’d get notified about any issues that arise in your game with as much context surrounding the issue as possible.

Let’s start by stating the obvious: an exception is a problem that occurs during the runtime of a program which disrupts its conventional flow and exception handling is the process of responding to an exception. In Android, not handling an exception will lead to your application crashing and you seeing the dreaded “App keeps stopping” dialog. This makes handling exceptions incredibly important, and let’s face it: no one is going to use an app that continually crashes.

A good developer knows how to debug code. In fact, most software engineers spend the majority of their time debugging existing code rather than writing new code. When it comes to native app development, debugging and tracking errors during development can be a tricky task. So, in this post, I’ll help you understand how you can debug your React Native applications and also track errors during app development.

Do your cron jobs (aka scheduled jobs) ever fail or not run as expected? Scheduled jobs are supposed to be predictable – as the name implies. But as with many things, predictable!= reliable. Cron jobs fail too and we think you should know when that happens, Crons allows you to monitor the uptime and performance of any scheduled, recurring job in Sentry. Once set up, you’ll get alerts and metrics to help you solve errors, detect timeouts, and prevent disruptions to your service.

Performance testing is an important part of any application. It helps developers to increase the application reliability while providing a smooth user experience to the end users. However, when it comes to Unity projects, games and interactive applications have a higher requirement for performance compared to traditional applications.

The mobile development ecosystem has always been very diverse, arguably more diverse than the web development ecosystem. While it seems like every day there are more frameworks and tools for web developers, a lot of them are built on top of JavaScript and implement similar patterns to each other. The mobile ecosystem, on the other hand, has a core set of languages that make the differences between mobile tools and frameworks much easier to identify.