By combining custom errors, named functions and Bugfender, you can create a robust error-handling process that allows you to immediately identify the defects of your JavaScript apps. Unhandled JavaScript errors will stop the execution of your script, leaving the application in an undesired state – or, even worse, in an unknown state. So you need a robust error-handling process to avoid unknown errors in your apps. But, why are errors thrown anyway?

Most of our blog posts are dedicated to Android, iOS and JavaScript development because those are the most interesting platforms for our users. However, from time to time, we also think it’s important to share what’s happening behind the scenes. In this post we’ll be highlighting some of the recent improvements we’ve made to Bugfender’s infrastructure.

Have you ever found yourself copy-pasting the same bits of JavaScript code between different projects? Well, when this situation happens two or three times in a row, it’s usually a good indicator that you have a piece of code that is useful and reusable. So, if you are already reusing your code across several different projects, why not go the extra mile and convert it into a library that allows you to optimize this code-sharing?

Node Package Manager, or npm (usually written in lower case) is one of the most commonly used package managers in JavaScript projects. It is built on top of Node and is so powerful that nearly everybody is using it.

Welcome to the Bugfender summer newsletter! As we already announced, we achieved a major milestone recently by releasing the Web SDK, bringing the features you love using to a whole new platform. But as always we want to keep pushing to give you a better product, and we’ve introduced recently some more updates we want to share with you: We hope you find all these updates useful!

When something crashes in an app, fixing the bug is usually quite straightforward. But apps can also be blighted by bugs that don’t result in crashes, and this is where things start to get interesting. To find and fix these bugs, you will require as much information as possible and probably a combination of tools. Let me explain a process we know as ‘bug forensics’, based on a real bug that has impacted one of Bugfender’s customers.

When you’re building a website that needs to be updated in real-time, your first thought is probably to add WebSockets to your application. However Websockets is a low-level protocol and to use it, you’ll need to add another layer on top to manage the information you want to get. This is where MQTT is handy, as it’s a higher-level protocol that simplifies working with data streams.

Today, May 21st, we received an interesting email from a journalist writing for Fast Company. Apparently, a privacy-focused company audited the app Care19, North Dakota’s COVID-19 contact tracking app, and they found that an anonymous tracking ID generated by the app was sent via API to Bugfender along with other identifiers. While the journalist contacted the app developers, he also gave us the opportunity to comment.

We are thrilled to announce Bugfender’s new javascript SDK for the frontend, which applies the simplicity of our mobile SDKs to web applications. Bugfender JS has all the features that you already know from iOS and the Android SDKs, enabling you to: In this blog, we’re going to tell you how to access our new SDK, provide a quick overview of its benefits, and bring you up to speed with the evolution of the Bugfender project.

OutOfMemoryException is a common and frustrating bug, and one of the prime causes of unexpected app shutdown. “Why is this happening now, if the app was working perfectly yesterday?” It’s a question which perplexes both rookie and advanced Android developers the world over. There are a variety of potential causes of OutOfMemory Exceptions, but one of the most common is the memory leak — the allocation of memory in the app which is never released.