Code of a global major's internal software gets leaked, a bank losing $500M, and tier 1 companies burning $900B in digital transformation. These are situations caused by software engineers like you and me.
HTTP request failures can occur when the app sends incorrect data to the server, delayed calls, exceptions thrown during an HTTP call or even executing duplicate HTTP calls. Developers need to be notified of such issues in real time.
Bug report stats from iOS and android apps for the year 2020
Appxiom provides a mechanism to monitor execution of functions in a defined sequence. This helps in monitoring features in Android apps.
Let us consider a scenario where your app user initiates a payment process in your Android app. You must have an integrated payment processing platform like Stripe in your app. The outcome of the transaction can result in either success or failure.
It is better to execute all time-consuming processes in Android apps like database operations, I/O operations and calculations through separate threads. This approach will help in avoiding such delays.
When iOS app consumes increasing amount of memory, it may lead to app crash. Appxiom reports high memory usage with data to reproduce them.
Manual bug detection and data collection in Android mobile apps during testing and development environment is time consuming and in production it is near impossible. Here is where tools like Appxiom aid the developers.
With basic integration, Appxiom is capable of detecting frame rate issues in iOS apps. To avoid frame rate issues, UI thread should not be burdened with any time consuming processes.
Wake locks determine whether the CPU or screen should stay awake or go to sleep. But using wake locks can create bugs that can drain the battery of android device. This article explores the ways to avoid such bugs.
The only way to avoid ANR in Android apps is developers need to ensure that the UI thread has very less burden and all time-consuming processes that take beyond 16 milliseconds are executed through worker threads.
Memory leak is a critical bug in watchOS apps, that often go unnoticed during development. Memory leaks can lead to EXC_BAD_ACCESS error and will manifest as app crashes in watchOS.
API bugs are the most common bugs in iOS and contribute 45% of all issues reported, followed by crashes at 25%. Memory leaks contribute 10% of bugs and came third in the list. Frame skips came next at 5%.
Crashes are the most common bug and contributed 33.3% of all bugs reported, followed by API call related bugs at 29.2%. Memory leaks contributed 16.7% of bugs and came third in the list. Delayed screen loading came next at 12.5%.
Showing 267–280 of 295 posts
