Force closing on android

How to Fix Force Close Android Apps Error on Android Phone

If you have an Android device then you may face some errors or bugs while using your device, these errors might be software related. Force Closing of Android apps error usually faced by most of the Android users which happens while using the stock apps, like if you want to open the Browser app for a quick search and what you might get is the force closing of app. This is a common problem with the operating system itself and it is possible to fix any software issue easily. Sometimes some kinds of errors can be fixed with factory reset/hard reset or any different method.

Here we’ve mentioned two easy methods to fix Force Close Android Apps if you are getting this error while working with Stock apps. But if the problem is with the third-party apps then you should navigate to Settings > Apps > App name > Clear Data. Now go ahead and follow the given methods to fix Force Close Android Apps Error on Android phone.

Solution 1:

1:- Remove the external SDcard from your Android device if you have already.

2:- Go to Settings → Backup & Reset.

3:- Here you can find the Factory Reset button, tap on it and confirm the to factory reset the phone.

It will wipe out all the data from the phone including your data and cache etc.

This method should to fix the force closing issue, if not then head over to second solution.

Solution 2:

1:- First, install the latest custom recovery like CWM or TWRP recovery on your device.

2:- After flashing a custom recovery, boot your device into Recovery mode.

3:- Tap on Wipe Cache to erase cache.

4:- Finally, tap on Factory Reset to perform.

This method will only Refresh the Firmware and Erase the Cache and the other data will be saved.

I hope that these two solutions will resolve the Force Close Android Apps Error on your Android phone but the both methods doesn’t work and still you have the same problem then it is recommended to flash the stock or any Custom Firmware to solve this problem without any doubt.

Don’t hesitate to tell us in the comments section below if you have any trouble or query while fixing errors on your Android device.

Источник

How To : Use Your Back Button to Force-Close Any Android App on the Spot

If you’ve ever used a custom ROM on one of your devices, chances are it had a built-in feature that allowed you to kill any app by long-pressing the back button. This function comes in handy quite often, especially in situations where an app is acting up, since it stops all associated processes and clears the app from memory.

Unfortunately, though, this feature is hardly ever present on stock firmware. So developer elesbb decided to create an app that will bring this functionality to almost any device or firmware, which means there’s one less feature you’ll have to miss about your old custom ROM.

Requirements

Step 1: Install ‘Hold Back to Kill’

To begin, point your device’s web browser to this link. The APK installer file should begin downloading immediately, but wait until it has finished before moving on.

Next, tap the «Download Complete» notification, then press «Install» on the following menu. When that’s done, go ahead and tap «Open.»

Step 2: Set the Timeout & Enable the Accessibility Service

When you first launch the app, you’ll be asked to set a timeout period for the long-press back to kill gesture. This is essentially the amount of time that you’ll have to hold down your back button before an app will be killed.

A value between 300 and 500 milliseconds should work for most folks, so enter your preferred number here, then tap the «Save And Close» button when you’re done.

At this point, you’ll be taken to your phone’s Accessibility menu. From here, select the «Hold Back to Kill» entry, then turn the service on and press «OK» on the popup.

Step 3: Perform the Gesture & Grant Superuser Access

The first time you perform the long-press back to kill gesture, you’ll be asked to grant the app Superuser access. This is a one-time thing, and in the future, the gesture will automatically kill the foreground app without any further interaction.

So open any app, then press and hold your device’s back button. When the Superuser request message comes up, tap «Grant» on the popup.

From now on, any troublesome apps are only a long-press away from being killed. Do you mainly use this feature to prevent apps from running in the background, or do you only use it when an app is acting up? Let us know in the comment section below, or drop us a line on Facebook, Google+, or Twitter.

Keep Your Connection Secure Without a Monthly Bill. Get a lifetime subscription to VPN Unlimited for all your devices with a one-time purchase from the new Gadget Hacks Shop, and watch Hulu or Netflix without regional restrictions, increase security when browsing on public networks, and more.

Источник

Android app force closes on start #264

Comments

famewolf commented Jan 24, 2018 •

Logcat attached. Device is a Leeco Le Pro 3. Error has occured on Omnirom, AICP and Paranoid Android for this device. (7.x Nougat) Fresh install. Using OpenGapps.

The text was updated successfully, but these errors were encountered:

kspearrin commented Jan 24, 2018 •

01-23 23:01:06.816 11841 11841 E AndroidRuntime: android.runtime.JavaProxyThrowable: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.InvalidOperationException: The configuration is invalid. Creating the instance for type ISecureStorageService failed. Key not yet valid —> SimpleInjector.ActivationException: Key not yet valid —> Java.Security.InvalidKeyException: Key not yet valid

Java.Security.InvalidKeyException: Key not yet valid

This is the error. For some reason that device doesn’t work with the Android Keystore. Any idea why?

famewolf commented Jan 24, 2018

Other than the fact it’s a no name phone no idea. Ironically I got it to work one time then could never recreate it so I know it CAN be done but not what was different. Do we perhaps need different lines in build.prop to tell it a different device?

mzarglis commented Jan 24, 2018

Same issue here. really sucks as i use the mobile app a lot. same device leeco le pro 3

famewolf commented Jan 24, 2018

Which Rom are you on mzarglis? Factory?

mzarglis commented Jan 24, 2018

famewolf commented Jan 26, 2018 •

I’m updating this because a user running the same rom was able to use the app. the two main differences were I was on opengapps mini and they were on opengapps stock. I also had magisk v15.3 installed. I flashed the same rom along with opengapps mini and it still crashed eliminating magisk. I’m now downloading opengapps «stock» to see if that resolves the issue.

kspearrin commented Jan 26, 2018

We’ve also seen this same problem on some older Samsung Devices (Galaxy S3 and S4). It’s still known why those do not work with Android Keystore either, but I’ve found several cases documented online by others also confirming the problem.

famewolf commented Jan 26, 2018

A clean install of AICP 12.1 rom (7.x) is able to install and run the bitwarden mobile app. It is the only rom I found that could do so among various I tried with both nougat and oreo bases. I have no idea what is significant.

mzarglis commented Jan 26, 2018

yeah it worked for me on AICP 12.1 before i upgraded to 13.1

famewolf commented Jan 29, 2018

I tried bitwarden on an Android Oreo Rom available for this device and got an identical abend. On the off chance it was a different error or explained better I’ve attached a logcat.txt from THAT rom.

kspearrin commented Jan 29, 2018

@famewolf It’s the same exception with the Android Keystore.

famewolf commented Jan 29, 2018

I’ve reported the issue to a couple of our Rom developers but not sure what priority it is with them since they don’t use bitwarden. If I reflashed AICP 12.1 where it works is there anything I could do that would help identify whats different about it against the other 7 rom’s I tried?

kspearrin commented Jan 29, 2018

Just share the above exception with them that occurs when trying to use the Android Keystore.

famewolf commented Jan 29, 2018

I did and even linked to this ticket but most don’t seem to consider it a high priority item since none of them use bitwarden and no other apps seem to have the same problem. For example lastpass works as expected. I appreciate all the time you took looking at this. Wish I could think of something to help resolve the issue.

janos-szenfner commented Feb 20, 2018

Same issue on Miui 9 with Android 7.0.

jaylittle commented Mar 3, 2018

I’m experiencing this issue on a LeEco LePro 3 X727 with LineageOS 15.1 cleanly installed. Note: I do not install Google Play Services nor do I have any intention of doing so. FWIW, Bitwarden’s mobile app worked just fine on the same phone with LineageOS 14.1 without Google Play Services.

famewolf commented Mar 12, 2018 •

I am on the 03/05 LeEco LePro 3 X727 with LineageOS 15.1 release which is the most recent official release. Bitwarden runs fine here so it does appear to be rom specific. I do have Google Play Services installed. (and did when I originally posted this issue)

jaylittle commented Mar 12, 2018

@famewolf We literally have the same setup except you have Google Play Services and I don’t. Interesting. FWIW, Bitwarden still crashes on launch for me with the 3/5 build.

esaavedra89 commented May 25, 2018

Some update of the issue or solution?

jaylittle commented May 25, 2018

Still happening for me even with the latest APK of the Bitwarden App from APKPure.

famewolf commented May 26, 2018

Not really much of an update but I switched to LineageOS 15.1 for the LeEco Le Pro 3 as well as opengapps mini and the issue went away. Opengapps mini was needed for google camera to work. Beangapps did NOT work so it’s possible it also had something bitwarden needed. Might be worth testing. I eventually had settled on just using lastpass becuase of the hotkeys to use default form profile as well as ability to add credit cards and select which one to fill. Was «clumsier» in bitwarden. I’ll re-evaluate farther down the line.

mzarglis commented May 26, 2018 •

The issue has been resolved for me as well since upgrading to AICP 13.1, now that i think of it i think i was using beangapps aswell and have since switched to opengapps.

But anyways no more force closes on my leeco le pro 3 on latest AICP 13.1 nightly with latest opengapps

jaylittle commented May 26, 2018

The Bitwarden Android app shouldn’t require Google Play Services (opengapps) to be present on an Android device and it appears that based on the other posts in this thread, it now requires exactly that. This is a disturbing trend that I hope will be reversed in short order.

kspearrin commented May 26, 2018

Play services is not required to run the app. We can run the app in a simulator without google apps and it works fine. There is also an f droid version if the app available in the releases page which doesn’t have any google play service libraries in it.

jaylittle commented May 29, 2018

So I did some digging after looking at the code for this and stumbled upon this issue:

It looks like somebody suggested removing the start and end dates from the keystore and somebody at the end confirmed that this resolved their very similar issue. I notice the bitwarden code seems to be setting both of them. Might this change be worth a shot?

jaylittle commented May 29, 2018 •

Also, I found the PR that was merged to deal with the issue on their end. Looks like a pretty simple set of changes. I’d do it myself, but I don’t have a proper build environment setup (Windows + Visual Studio) to do and test the work myself.

kspearrin commented May 29, 2018

I created a build them them removed: 14d1d13

Our CI system is having issues at the moment so I can’t provide a apk yet. Will be available here when that starts working: https://ci.appveyor.com/project/bitwarden/mobile/build/artifacts

kspearrin commented May 31, 2018

jaylittle commented May 31, 2018

Wow. That worked. Using that fdroid apk, I was finally able to actually use BitWarden on my LeEco LePro 3 phone with Lineage OS 15.1 sans Google Play Services for the very first time. Thank you! Hopefully others in this thread can confirm this fix as well and experience some relief.

kspearrin commented Jun 4, 2018 •

This is pushed to the latest play store beta. Will go out in the next version.

SamuelGeiger commented Jun 27, 2018

This issue is not resolved. I try to use the app on a Sony xperia z1 with the latest stock rom and it crashes every time on Startup. I don’t have my phone rooted so I don’t now how to obtain any logs. I did send two crash reports.

mjarsenault commented Jan 16, 2019

Has there been a fix for this yet? I’m on a Le Eco Pro 3 with the latest AICP 14.0 ROM installed, and Bitwarden wont even open.

I’d really love to use it but won’t be able to without it working on my phone!

kspearrin commented Jan 16, 2019

@mjarsenault Do you have at logs available from the phone?

mjarsenault commented Jan 16, 2019

@mjarsenault Do you have at logs available from the phone?

(I hope I did this right)

famewolf commented Jan 16, 2019

On the Leeco Pro 3, the problem appears to be some of the Rom’s available. For example Lineage 15.1 does not give the error nor does the latest AICP as far as I know. You seem to be on an older version? Try one of the ones with Oreo or Pie and the problem should go away. I personally run Lineage 15.1 (and am looking at Lineage 16..given you’ll have to do a clean install to jump a version you might as well go all the way to pie) on my LeEco Pro 3.

mjarsenault commented Jan 16, 2019

I’m on the January 10th (latest) release of AICP 14.0, which is a Pie ROM.

famewolf commented Jan 16, 2019 •

I’m on the January 10th (latest) release of AICP 14.0, which is a Pie ROM.

Interesting. Well obviously something has changed then because I recall reading earlier users on AICP saying it was working at the time. perhaps it worked on AICP Oreo and doesn’t work on pie. Perhaps you can point out the issue to the rom developer and indicate the app DOES work on Lineage15.1. It’s possible he can find out what the issue is. I would also perhaps try a couple of different gapps versions (I’m on opengapps mini).

Realistically there is not much the bitwarden guys can do since on factory rom’s the app will work as it should and the problem appears to be specific to custom roms/versions. (sadly ALL our rom’s are considered custom since the manufacturer abandoned support back when it was on marshmallow..it’s still a heck of a device and the price for me was hard to beat)

Источник