Every once in a while I get:
Unfortunately, MyApp has stopped.
Problem is easy to solve if you have some logs, but in my case logcat has absolutely no message of error (it has normal messages published by my app and other exceptions are shown there but not this one which causes this app has stopped).
Is there any chance I can solve this problem?
The good thing is I can quite easily reproduce it, thus I'm trying to put as many information I can to logcat and then investigate what happened.
I have ACRA up and running (other exceptions are caught by it but not this app has stopped).
When it happens my app is not visible and there are some things happendnig in IntentService. My app is tracking geofences and the app has stopped happens only on HTC M8 when I switch on and off Location in phone Settings. I've tested on different phones and it does not happen on LG G3, Nexus 5, Moto G, LG Swift L9.
Did you try to run LogCat in command-line? You might be able to see the error. Android LogCat in command-line
If your using Eclipse as IDE, try checking your filters for LogCat. You may accidently not displaying errors in LogCat.
Try finding the error via the Debugger. Place breakpoints to places where you suggest the error to be.
In my case logcat was filtered. You can change filter in
Android Monitor -> logcat -> Bottom right corner, change filter to No Filters. It will show all errors.
It sounds quite trivially - try to restart computer, test at other emulator or device. Also you can add your try-catch block and forget to type e.printStackTrace() or use UncaughtExceptionHandler.
It's very weird,that you are not able to find out any logcat. So why don't you try Hockey app.Please go through the guide.I think you can use it for some time.After that you have to pay for it.
Good Luck.
Related
I am very new to Kotlin and Android studio. I tried running my App through the emulator, I built in AVD manager.
Whenever I run my App it goes to the home screen, I don't know what you'll need to solve this or what causes it:
But based on what I've seen as I researched this issue, here are some info I think you might need;
-I've turned off detect adb location and set the directory to C:\Users\user\AppData\Local\Android\Sdk\platform-tools
-minimumSdk 21
-targetSdk 31
-My Api level is 25
Please whatever info you need to help me rectify this issue just ask me..
I am open to any suggestions, Thank you in advance for your help!
here's a screenshot of build error:
I'm adding a logcat error message screenshot, though they are much of error I just screen the ones that could be taken on a single shot, I hope it enough.
(Please note that previously my logcat was empty even when I was experiencing the same problem, so I created another emulator, and the logcat is no longer empty..)
You can check out the logcat to be able to see what went wrong.
Testing on Samsung Galaxy Note Edge, Android 6.0.1
PLEASE NOTE - this issue happens only on Samsung Phones with pre-installed "Smart Manager". If you have no experience with that constellation, please read in detail whats the real issue. This is irregular, not a usual debugging thing. Please don't expect a code snippet right now, there cant be one. At this point I cant post any reasonable line of code because the origin of those errors is COMPLETELY UNCLEAR. I have only 4500 lines, and 25 classes, but absolutely no clue where to pick a meaningful snippet from without any hint what Smart Manager complains concretely. It says just one word: "ERROR", but not when, not why, not what ... Mission Impossible 😩
I've researched a lot now, but found almost nothing being of help. My app is compiling fine without errors and running smoothly (and very fast!) as desired. I cant feel anything about "performance degradation", but Samsung "Smart Manager" has this very weird issue with my app...
Battery lasts for days on standby, no heat, nothing notably.
No information what kind of error should have been occurred at all. No more details to open, simply nothing!
My app does definitely not run in background. It stops, pauses and resumes without issues. No issues, no errors during building (Android Studio 2.2), no warnings about Smart Manager performance issues, this error pops up ONE WEEK LATER, or two or three. That's why I you have no chance to create a link between error and possible root cause to start tracking down. In that time you made lots of code changes before you get notified from SM the first time, lots of Git commits, but which one contains the change this external tool complains? That makes it a real hell.
I also let it connected for 5 days to USB, collecting tons of logs, crawling the logcat like crazy for any relevant events, but SAMSUNG's Smart Manager doesn't seem any need to log at least one word when it counts its ominous errors.
What I've found on the net, nobody really knows how to debug this, just very time-consuming guesses which I followed where applicable - without success.
What I've already tried:
Exceptions - all caught and handled
Removed all debug logging output
Checked for infinite loops
Checked for missing or damaged resource files
Disabled auto-translation
Checked for whatever could be irregular, suspicious or extraterrestrial 👽
And after making changes I must wait days or weeks if it will finally pop up again or not...
Could there be any way to catch those Smart Manager error count events and attach some whatever sort of logging to it? There is no documentation from Samsung anywhere, no support for this pre-installed app, no help at all.
The error message is very clear, 10 crashes in 1 week. I would clearly say that the app is sub standard.
You should start with implementing a Global Exceptional Handler or start using some specialized service such as "Crashlytics" in you App to understand what is going on.
I've been programming some Kivy/Python apps on my Motorola Moto G mobile phone.
I've got a few handy little apps, that have been working OK for a few months.
Today, I launched one of the apps - through the QPython interface, and it didn't work.
So, I tried another of my apps and that failed to launch for the same reason. In fact, all of them fail to launch for the same reason.
The error shown on screen ends with:
File "/QPython/core/build/python-install/lib/python2.7/UserDict.py", line 23, in getitem
KeyError: 'ANDROID_APP_PATH'
I presume that something on the phone has taken an upgrade - and broken something.
I assume that is the case because this problem affects all of the Kivy apps I was using.
Anyone else encountered this?
You need to have
#qpy:kivy
part in the first line.
At least that was what happened to me.
I suppose that is because QPython is finding what type of app is it.
What does this error message mean?
setWindowSurfaceColorBuffer: bad color buffer handle 0
My app works fine and it does not seem to be affected by this message in console output in Eclipse. Is there some way that this message is affecting my app in producing best results?
I ran into this recently, it appears that it is a bug. All I did was restart my emulator and run the app again.
I had similar situation but after much search, I progressed with the project and it still worked perfectly. So, I think you should just ignore it.
I had exactly the same error.
The best way to go is to wipe data from your emulator.
This worked for me and hopefully will work for you too.
I am trying to wrap my head around Android Widgets, using the sample provided here: http://code.google.com/p/wiktionary-android/
I have corrected the strings.xml but the plugin will not work properly, neither on the emulator nor on the actual phone. It installs fine, but it never updates.
But at least on the simulator i get some DDMS output, telling me, that the API-response could not be parsed, so I assume, that the Wiktionary API has probably changed.
However, on my phone, the public void onUpdate(...) method doesn't even seem to get called at all when I install the Widget. I have inserted Log.i(...) lines for debugging and while they all show up when I use the Widget on the emulator, none of them seem to come up when it actually runs on the phone.
The phone is a Samsung Galaxy S II running android 2.3 but that hardly matters I think.
has anybody encountered this before and knows anything that might help?
EDIT I was told it might be a permissions issue, but could not verify this.
OK. Just in case anybody else ever comes across this. There is a strange thing with android widgets when the throw an exception... just uninstalling isn't always enough one hast to restart the phone.
Can not explain why that is but it always did the trick.