My app has been working quite happily with Android Wear support for the last two years or so. Following an update to Android Webview, I'm getting force closes in some circumstances when running my app. The force close is within the Android Wear component though. My software hasn't changed (and I don't think I'm using a Webview at all, though Wear may be I suppose). I'm not really sure how to go about debugging this, other than keep on reporting the issue via Android and wait for Google to fix it (if indeed the bug is within Android Wear or Android Webview itself). Here's the stack trace. Does anyone have any ideas what's causing it please? Any help gratefully received.
Related
I am struggling with a strange situation with my Android app.
It runs on a 5.1 OS and the device is Rooted.
The app is running fine for a few days and then from an unknown reason it crashes (WIN DEATH without any exceptions from my logs).
I think it related to an internal memory leak on a specific Android model I'm using.
Anyway, I need to restart the app in cases like that.
Unfortunately, using 'Thread.setDefaultUncaughtExceptionHandler' method doesn't help because it won't handle those situations (the app is crushed).
I thought about creating a second app that samples the state of the process and if it is disappears from the process list, it starts the activity.
Is there a more elegant way to handle this situation?
Thanks a lot!
Asaf
I'm developing a Spotify-app on Android. The app already runs on Nougat and Oreo, but I'm still having problems with Android 6.0.
The Problem is if I install the app via Playstore, I'm stuck on the loading screen because I don't receive a correct response.
But now, if I install the exact same app from Android Studio, it works without any problems. This also makes debugging very difficult, because I can't use the debugger for Playstore apps.
Do you have any Ideas why? I've got the same problem on all 3 devices that run Android 6.0
I don't really have an answer for that, but I can't even get that far. Which Spotify API are you using? If you're able to get it to get that far, I may have hope haha
An app I published crashes on certain specific devices. I keep receiving messages from the users that just "can't open" the app. This of course lowers the rating on Google Play.
On Android Vitals there's no reference of these crashes, all crashes I receive are managed and happen after the app start, but if I filter for device model or Android version looking for those that tell me that the app didn't open, I find absolutely NOTHING.
I installed crashlytics, and I was astonished by the fact that I received completely different error communications, so Android Vitals seems just partial?
And anyway, still NOTHING about early crashes.
I tried to install the app on the official Samsung online emulator for some devices that are suspected to crash, and still... guess... NOTHING. So I can't even test it and I'm completely helpless.
How can I do to stop this bad app behaviour, that reduces the number of my happy users? I need a really reliable way to detect ALL crashes.
thank you.
Use a Crash Reporting Tool such as Firebase Crash Reporting. Everyone professional uses such tool
https://firebase.google.com/docs/crash/
As already mentioned, you can use a crash reporting tool/framework, additionally you should be aware, that offline crashed might not get reported and if the user doesn't allow you to use the internet, there is no way around that, as far as I'm aware.
In the meantime you could try excluding the devices that you suspect to produce crashed while you are trying to fix it (if you care about the rating).
First question, appreciate some guidance. I am currently teaching myself to develop for Android and have installed my app (via Studio after builds) onto my own phone.
Every now and then my phone will restart itself (not querying that - these things happen).
During these (occasional) restarts I will get a message that Android is "Optimising App 1 of 1". I am pretty sure it is my app being "optimised".
I have searched here and the Web. Most of the questions seem to be users that have recently upgraded OS Version and that is causing the issue. There seems to be anecdotal evidence that wiping the cache cures this and that it only does it while the device is being charged.
However, if it is my app, I don't want users of my to go through this. I suspect it relates to the Target SDK I am using but it might be something different?
So, what is Android optimising? How can I make best efforts to stop my app being the cause of this?
Many thanks.
Earlier Android OS used to run on Dalvik Runtime which means apps used to compile at the time of execution. But now, Android has switched to ART with Lollipop version. It means all the apps will be compiled beforehand making them launch faster. So "Optimizing the Apps" basically means Android is compiling all the apps.
From Android 5.0, Android uses ART instead of DVM So every time your mobile OS upgraded This will happen. Also “Optimizing app” should happen only once after OS upgrade. If it’s happening every time then there is some issue in your mobile.
A factory reset should be probably solving this. (You have to go
through the pains of redownloading all your apps etc).
I have developed a Ionic app that uses Android Speech Recognition API via a Cordova plug-in. It worked fine a few days back, but one day it stopped working. I did not change any source code. Sometimes it immediately returns me an error: ERROR_NO_MATCH. Sometimes it worked for one second, gave me one or two words and stopped listening abruptly, regardless that I was still talking to it.
I reflected what has happened in recent days that may have caused problem.
Changes to Google speech recognition server? It is not likely. I did not
find anything about it from the web. But a weird thing is: I installed some other simple voice-to-text apps, they all seem to terminate listening prematurely.
Changes to my computer? I have re-imaged my hard drive and reinstalled everything.
Changes to my mobile phone? Maybe some auto update has affected the voice recognition part.
Anyone has the same problem? Any help is appreciated.
Edit 08/09/2016
What I have tried:
Factory reset of my mobile phone
Building the app with different Android API levels
Uninstalling all updates to Google App, and disabling it
However, none worked.