What to do when android app crashes

How to Fix Apps Keep Crashing on Android Devices

by Jenefey Aaron Updated on 2021-03-23 / Update for Fix Android

Gmail and regular Email application is constantly crashing as of 12pm today March 22nd. App stays open for 5 seconds before closing automatically. Issue consists after two restarts and cache cleans.»

Previously On Android Apps Crashing

According to Downdetector on March 22nd, many Android users claim that Android apps like Gmail keeps crashing. Now the chief culprit seems to be the Android System WebView. What is Android System WebView? It provides Chrome-like browser rendering within apps. And Google is working hard on this Android Apps Crashing Issue.

Most of the time it can be fixed but other times app may have bugs memory leak issues which can’t be solved on user’s end. Those kinds of crashes are only fixable by developers. I will cover how to fix Android apps keep closing unexpectedly, and you can try the solutions given below to fix app crash Android.

Part 1: Repair Android System to Fix Apps Keep Crashing on Android -100% success

Why do my apps keep crashing Android? This can be caused by many reasons such as corrupted os, inadequate storage space. No matter for what reasons, Tenorshare ReiBoot for Android provides one tap solution to repair Android system to fix app crash problems with 100% success.

Launch ReiBoot for Android after installing and connect your Android device to your computer via USB cable. Click on ‘Repair Android System’.

On the following screen, you have to click on ‘Repair Now’ button.

Enter your device information such as brand, series, model, country and carrier, and click on the ‘Next’ button to download the firmware package appropriate for your device.

When the downloading is done, on the screen, click on ‘Repair Now’ button. A pop-up message will appear where you have to click on ‘Continue’ button.

Following the on-screen instructions and perform the action required accordingly. After repairing, you will receive the message ‘The repair process is completed’.

Part 2: Other Common Tips to Fix Android Apps Keep Closing Unexpectedly

There are also some other ways that proves to work for fixing apps crashing on Android phone. Follow our guide and have a try.

1. Uninstall Android System WebView

As we have talked about before, if you accidentally run into Android apps crashing, then you can try to uninstall Android System WebView on Google Play Store.

• Navigate to Google Play and Tap on the My Apps & Games.
• Then find Uninstall and go to Android System WebView.
• Just uninstall it.
• Restart your Android phone.

2. Restarting your Phone

Yes! You read that pretty right, this may sound simple enough to work but trust most of the time app crash issues are solved by simply restarting your phone. This happens due to a number of reasons, when your device stays on for a long time like 2 or 3 weeks, background services and some apps start to use a large portion of your phone’s RAM. Android memory manager(LMK) takes care of memory most of the time but the problem is more likely to occur on low to mid-end devices.

Restarting your phone will clear all the apps clogging memory and fix apps freezing and crashing on Android device. It is a good idea to restart your phone after a week because it may sound silly but it will keep your Android device healthy.

3. Clearing App Cache

Another reason why your app may be crashing is insufficient cache space or corrupted cache, Almost every app use cache memory to save some of its data. More importantly, if you are using any app very often then it may start to misbehave after a week or two. Cache data is stored in the form of chunks, device with low speed, internal memory may perform sluggishly due to the overhead of reading huge cache. Many users have reported that clearing cache fix crashed apps on Android devices. This is how you can simply clear app cache:

• Open Settings on your phone
• Navigate and find Apps section in your settings and tap on it
• Now a list of apps will be shown, find the app you want to clear cache and tap on it
• Now find the button saying clear cache, if you have latest Android OS then clear cache will be in storage menu of app

Once you have cleared the cache, your problem will be more likely to be solved but its goof to restart the device after clearing the cache.

4. Clearing App Data

This solution is same as clearing cache, the only difference is that you will lose your app configurations. For example, if were logged in the app, you may have to sign in again, it’s like running the app very first time after installing it from Play store. Clearing app data is more likely to fix app crash on Android phone. We recommend you to try clearing cache first if the problem persists then clearing app data won’t hurt. This is how you clear app data on any android device:

• Open Settings>Apps
• Find and tap desired app
• Tap storage menu and find clear app data button and tap it

5. Updating Apps

Most of the time apps tend to misbehave if they are outdated and face compatibility issues with Android OS or other apps. If your apps are freezing frequently then it is time to check for updates. It is a good thing to update all of your apps as soon new updates hit in, this is how you update apps:

• Open Play store
• Tap three lines icon on top left
• Tap My Apps and Games
• A list of app will be shown having update button after each app that can be updated, selectively update the app or update all apps by tapping Update All app button on top

6. Wiping Cache Partition

If your Android apps are running slow then wiping the partition can fix those slowdowns and sluggishness from your phone but in order to perform wipe cache partition operation, you will need to enter Android recovery mode of your device. Different devices have different key combinations need to be pressed in order to switch into recovery mode. Most of the devices use Power Button and Volume Down keys. This is how you wipe cache partition of your device:

• Turn off your phone
• Now press and hold power key and volume down key
• A menu will be displayed, now follow on screen instruction to log into recovery mode
• Once you are in recovery mode navigate and select Wipe Cache Partition Option using volume keys to move up and down and Power button to select
• Confirm the selection
• Restart your Phone

Conclusion

Now you have mastered how to fix apps keep crashing on Android devices. Hope those solutions are able to cope with your issue. Welcome to share this article with your friends and discuss more methods. Thanks for reading.

Updated on 2021-03-23 / Update for Fix Android

Источник

Are your Android apps crashing? You’re not alone. (Update: Fixed)

• Android apps are randomly crashing for some users.
• The issue seems to stem from a bad Android System WebView update.
• Google has issued new Android System WebView and Google Chrome updates to address the issue.

Update: March 23, 2021 (4 AM ET): Google’s Workspace status page indicates says that the problem with Gmail on Android is fixed.

The company says updating Android System WebView and Google Chrome via Google Play Store should now resolve the issue for all users. The Play Store listing for WebView shows Google has pushed out a new version of the apps (ver. 89.0.4389.105). Chrome has also received an update today.

It’s unclear whether this fixes problems with other Android app crashes as well. Nevertheless, you should try getting the new versions of both apps to see if the issue is resolved. Else, read on for possible workarounds.

Original article: March 23, 2021 (12:12 AM ET): Android users have been experiencing random app crashes over the past few hours. Apps like Gmail, Google, Yahoo Mail, and others are constantly shutting down and behaving erratically. However, Google is aware of the problem and working on a fix.

In a statement to multiple publications, a Google spokesperson said, “We are aware of an issue with WebView causing some apps on Android to crash. We are currently working to fully validate the scope and a fix is in progress.”

The bug seems to be impacting all Android apps that use the WebView system component. Google apparently pushed out a bad update to WebView, resulting in Android app crashes.

Some users have found removing the latest WebView update or uninstalling WebView entirely fixes the issue. Samsung’s official US support Twitter account also recommends removing the update.

If removing the update doesn’t work for you, try uninstalling WebView. To do that, head to the Google Play Store > My Apps & Games > Installed. Android System WebView should appear in this list of installed apps. Tap on it and hit uninstall. You should then reboot your Android device for the best results.

Remember to reinstall the latest version of WebView once Google fixes the issue. It’s an important component that lets apps display web pages.

Meanwhile, if you’re trying to access Gmail, you should use the desktop interface for the time being. The company has also
acknowledged the problem with Gmail on Android on the Google Workspace status page.

Источник

How to avoid delivering a crash-prone Android app

This blog post has been adapted from a popular conference talk given at DroidCon SF, AnDevCon, and various other company conferences. Learn about the common reasons Android apps crash and key takeaways for how to avoid them.

Whether you’ve recently launched an Android app or are in the process of building one, every Android developer quickly discovers a fundamental truth: crashes are your worst enemy. Not only are they harder to prevent in native Android apps than in iOS, but crashes are also more likely to occur.

Before we dive into six reasons why these failures happen and how to defend against them, let’s start with some basics about bugs and user behavior.

Know thy enemy

Do you know the dirty little secret of software development? It’s a simple, if rather unfortunate, truth: you cannot fix every bug. No matter how much you try, bugs will always exist.

What you can control is identifying the most harmful issues and collaborating to fix them as quickly as possible. Not surprisingly, crashes qualify. They matter a great deal, and here are two reasons you want to minimize their occurrence:

1. Users are quick to abandon apps, even when they perform flawlessly. One in five users abandons an app after only one use. Before you say, “Well, that’s not too horrible,” keep in mind that the first use is only the initial hurdle. The average app loses 77 percent of its daily active users within three days of installation, 90 percent after 30 days, and more than 95 percent within the first three months. Tough audience.
2. You’ve got stiff competition. Whether you know it or not, an alternative to your app exists in the Android app store. With 2.6 million apps available as of December 2018, users can easily find a replacement if yours disappoints. When consumers have options, the pressure is on you to deliver a quality product, and a substantial part of that promise is stability.

Crashes are cause for a break-up

Given those scary user retention numbers, it’s imperative that your app make a strong impression from the get-go and then continue to provide a crash-free experience. Users have a very low tolerance for crashes, and a full 84 percent will abandon your app completely if they experience two crashes.

If you still have your doubts about the seriousness of a crashing app, peruse the comments section in Google’s Play Store on a couple low-ranking apps. What you’ll discover quickly is that crashy apps make for cringe-worthy fodder (although this feedback is obviously not-so-fun for the app developer).

In short, trust goes out the window when an app crashes, and along with trust is the app’s reputation. A crash is a death knell and demonstrates why you must care about production monitoring from the very beginning.

Pro tip: Adopt a stability monitoring tool like Bugsnag to set stability goals, get a handle on bugs, and rank them by impact.

Six reasons Android apps are crash-prone and what to do about it

As you likely know, building client-side software means your apps are running in an environment that’s out of your control. While server-side you can determine hardware, operating system, and which version of your app is live, none of that holds true client-side.

Think of client-side as the Wild West. Roughness, lawlessness, and disorderly behavior prevail. As befits this environment, there are six reasons why your Android apps are crash-prone. Thankfully, there are (usually) steps you can take to address the challenges.

Reason #1: Fragmented hardware

Unlike iOS hardware, which Apple keeps on a notoriously tight leash, Android devices multiply like rabbits. In fact, more than 24,000 unique Android devices were counted in 2015, which was six times as many as three years before in 2012. The situation has only intensified in the last three years, so it’s safe to say that Android app developers are dealing with an incredibly fragmented hardware environment where many old versions are still in use, including phones from 2009.

Yup, phones from ten years ago are still in use. And, yes, that is scary.

What that means is that your app needs to run on devices with different CPU architectures, varying CPU and memory constraints, and that lack hardware features you might naturally expect (camera, Bluetooth). Because Android devices are often found in emerging markets and developing countries, there are many versions out there that cost less, have cheaper components and CPU, and have low amounts of memory. How do you handle these scenarios?

Actionable defenses: You have a couple options that can help safeguard you from disappointing a user.

• Detect features pre-download. Use the [CODE] [/CODE] element in your app manifest to filter your app so that it doesn’t show up for users whose devices do not meet your hardware and software requirements. For example, if a device doesn’t have a camera, then you won’t show up in that user’s app store options.‍

• Detect features at runtime. If the feature or hardware need is non-essential to your app, then you can push off the decision until runtime. In other words, if the user attempts to use the camera but there’s none available, the app can check and then tell the user they don’t have it available. This scenario is a much better user experience than a crash.

Reason #2: Rooted devices

It’s much easier to gain root access to the Android operating system, which leads some advanced (and sometimes not-so-advanced) users to tweak their phones and tablets in unpredictable ways. When various subsystems and settings change, the components your app relies upon may be inaccessible. For example, rooted devices may block access to certain permissions at runtime, which inevitably leads to crashes.

Actionable defense: Your best defense is to detect rooted devices at runtime. It is possible to use root detection techniques and thereby restrict access to certain features and functionality within your app. Alternatively, some companies stop the app from working at all on rooted devices to avoid the dreaded crashes.

Reason #3: Multiple Android versions

What’s the only thing more frightening than how many different Android devices are being used? That would be the number of operating systems currently in use. While Android lists thirteen platforms with more than 0.1% usage, it’s striking to note that the Marshmallow platform from 2015 is the second most widely used version (21.3%) behind the current Oreo platform (21.5%). Even though Marshmallow is over three years old, it’s still going strong, as are the two platforms that preceded it (2014 Lollipop at 17.9% usage, 2013 KitKat at 7.6% usage).

Needless to say, people in Androidland do not upgrade (and sometimes can’t do so even if they want to due to carrier settings), so it’s guaranteed that your app will run on multiple platforms. The question is, how many? The Android developer website recommends supporting 90% of active devices, but targeting your app to the latest version.

Actionable defenses: Once again, there are several best practices you can follow.

1. Specify supported versions in manifest. By identifying what the minimum version of Android is that you support in the manifest file, you can prevent your app from showing up in the Android store for any users with prior versions.‍
2. Detect version at runtime. If the API call is non-essential to your app, then you can push off the decision until runtime. For example, you can check for either a feature or the platform version at runtime and then disable particular features depending on the environment.‍
3. Use the Android Support Library. How would you like to make it seamless to support multiple API versions without sacrificing new features? When you embed the Support Library into your app, you can leverage it as a compatibility layer to older Android versions. That means less code to build and happier users who are supported appropriately in whatever version they use. In short, you don’t have to wait for your customers to upgrade, which is a reason to rejoice.

Reason #4: Vendor modifications

Well, this reason is terrifying: phone manufacturers can make modifications to core parts of the Android operating system. Not surprisingly, when core parts are edited, it can lead to crashes in your app. One example came about when HTC shipped their own version of GSON as part of their Android fork, which was super buggy and caused major issues with apps. The result? Crashes, of course.

Actionable defense: Sadly, there’s not much you can do about these types of crashes. Your only line of defense is to use a stability monitoring tool like Bugsnag so you can at least see what the problem is when this type of crash happens. Otherwise, the best we can say is…

ВЇ\_(гѓ„)_/ВЇ

Reason #5: Multiple live app versions

Here’s a frustrating fact of client-side applications: customers do not update apps immediately. While it’s getting better these days with Android’s automatic updates, there’s still the potential that multiple different versions of your app can be live at the same time. You need to make sure the language they are speaking is the same language your service is speaking.

Actionable defense: Thankfully, this defense is relatively straightforward: version your APIs from day one. Any app that accesses network services must be backward compatible.

Reason #6: Out of memory errors

Our final crash reason happens to be the bane of developers’ existence, and even a stacktrace for the error won’t be helpful for solving the issue. An out of memory error is thrown when there is no memory left for your app to use. Keep in mind though, the last memory allocation that triggered the error is not necessarily what caused the memory leak, which is why the stacktrace won’t help you. Instead, prior memory allocations added up, and it was only the last one that reached the threshold. Think of it as the straw that broke the camel’s back.

Actionable defense: There’s a tool called LeakCanary that was built by the team at Square. It detects memory allocations and can spot when this scenario is occurring. LeakCanary has been billed as a memory leak detection library for Android (and you’ll be happy to know there’s a Bugsnag integration for it as well!).

Don’t let crashes get you down

The heartening news is that you’re not alone. Crashes happen to every app. In fact, in our experience, even high-quality applications crash between 0.1-1% of the time, and that’s okay.

Crashes are a part of software life, but they don’t have to ruin your app’s chance at long-term existence. Come prepared, put up defenses like the ones described above, and never fly blind in production. Use a stability monitoring tool like Bugsnag to make sure you know your bugs and can stop the ones that make you crash-prone.

Now go forth and conquer Androidland with your crash-resistant app!

Источник