So I just released an app to market (won't plug it here)
I tested it on about 5 devices, no problems. I publish it, and pretty quickly an XDA member (Izkata) gets Force Close on Samsung Galaxy 2.1(froyo)
It works on Emulator for 2.1... how do I go about figuring out what the problem is?
I'm thinking PM Izkata for DDMS exception info, but this approach requires effort on users' parts.
Really stumped about how to re-create Force Closes, any tips?
Thanks
Phil
I have so far developed 0 android apps, so I don't know how to do this, but I have seen some apps that will send debug information to the developer.
Try this:
http://www.cyrket.com/p/android/com.xtralogic.android.logcollector/
They'll be able to send you the log after the crash.
If he installed it with the market, when the app force closes he should have three options: force close, wait and report (send report or something like that). Ask him to send the report and you should see it in your market account.
There are other ways about implementing automatic sending of force closes to you, but would require some coding.
Related
After using the S7 in the A1 version for a while, there is a couple of questions arising to me:
I did the mistake of installing Twidroid PRO which now withstands all attempts to get removed. Even worse, it will start in the background every time I restart the device. I really want to get rid of Twidroid.
Whatever I do, I cant get any QR reader to work. After googling for the problem it seems, that some other S7 users experience the same trouble, while others dont. Maybe depending on the type of camera installed. Any ideas?
Some very basic applications, like Google Goggles, are not visible for S7 users in the Android Market. A few can be found on alternative sites and do work fine, but most apps stay unreachable. Is there a way to get those apps ?
Thanks for any hints to get more happy with my S7.
as for twidroid, root your device and uninstall it once its rooted, I will take a look at getting google goggles tonight and let you know
Thanks for your help. I did root the S7 and after some more fruitless attempts to delete Twidroid, I found the reason - but not the solution:
Twidroid disguises as a system file that resists any attempts to delete or to uninstall. Basically, the typical behaviour of malware.
This makes me even more worried about Twidroid and its "mission".
Removing system apps
Hey Ossyris,
Did you check out:
forum.xda-developers.com/showthread.php?t=942166
He seems to be removing twidroid "rm Twidroid.*".
Personally have not done this yet... but I will soon.
I have a user of my app who is having a problem running it. My code launches another activity in the same app, and he is saying it is stopping before it should & returning to the previous activity, and he doesn't see any Force Close warnings.
I have run my code in the emulator & on my phone, I can't reproduce the error. We both run Android 2.2 on our phones, his is an HTC EVO & mine is a HTC Wildfire, as far as I can tell his specs are better than mine so shouldn't cause an issue - I deliberately chose a low spec for for my dev work so the code ought to run on anything.
As a bit of an Andoid dev noob (but been coding for years), is there any easy way I can make a special build of the app to send to him that would log any errors that happen ? I'd like to get a stack dump as well if possible, as I'm not sure exactly what routine in the activity its crashing out in. The activity that crashes is Gallery with 9 images in it, he can't flick through them or select one. I'm stumped as to whats causing it, any assistance would be gratefully received.
Thanks.
Why not point to your app and let others here try it on their phones? It could simply be other apps installed on his phone interfering with your app.
Long time programmer here too and when I get to where you're at (and I"m sure you've put some hours into this LOL), I go back to STEP 1.
I comment-out any and all code but the bare minimum; break it down to the Intent, startActivity and maybe a Toast message in the second activity. Even parse down your XML files to bare minimum.
See if that works. Then, ADD BACK ONE LINE OF CODE AT A TIME Run program and make sure it works. Yeah, it's painful, but in my 20 years of coding, I've learned to put my pride aside and to not "pretend" all the code I've written is correct.
Sometimes on bigger projects, I"ll change or add a couple of lines of code, run a back up and test. Rinse and repeat LOL. That way, I know I"m only a couple of lines of code from what "used" to work.
Good Luck!
Thanks both of you.
old_dude - Its a paid app. Only £0.99 but I don't think people would pay to help me. There is a free version of the same app (with less functionality) that this guy can get to work. If your really interested the 2 versions are -
Plink Log - Free Version
Plink Log Pro - Paid version
Rootstonian - agreed thats the approach I'd normally take if I was having problems on my dev phone or the emulator. The problem is that its OK on my HTC Wildfire/Android2.2 but on this guys HTC EVO/Android2.2 its having problems. I dont really want to keep sending him .apks with 1 or 2 lines extra enabled just to see if that fixes his specific issue. I was hoping there was something I could code to catch whatever crashes the activity & log it somewhere for me to analyse. When I do PC dev work, I have a global exception handler that catches anything I dont explicitly handle, and dumps the full call stack into a Log File I can read later.
I think I'll just have to take the existing app & put loads of debug code into it to save messages into a log file & see what bits of code are being called & what isn't & then get him to email me the results.
Thanks for the ideas guys, its always useful to get input from another perspective.
Dave
Hmmmm, just discovered setDefaultUncaughtExceptionHandler - might be able to use that with printStackTrace. Sounds interesting.
I have a problem with the Acer "apps" on my a500.
when I launch the eReading, Games, Social and Multimedia shortcuts I get a force close on the process "ApinAp (process android com.acer.app)" I have tried to clear data in "ApinAp" but it did not help... it worked when I bought my A500 a week ago.
but I don't know when it stopped working.
if anyone have a solution or a good idea to try please don't hesitate to answer ;-)
Reset it. There's probably a bad app having it's way with your tablet and causing the instability. If it continues to happen on stock, send it back.
Start installing your apps back one by one with time in between to test. Eventually you'll be able to track down the one app you shouldn't be using.
I have the same problem. After rooting, I restored *a lot* of the backups from my 2.2 phone. I uninstalled some because they didn't play nice with honeycomb, but I still haven't been able to find the culprit. Also, restoring the backup from their original, pristine condition did not help. I would really appreciate it if anyone knows which app(s) is/are responsible for this.
Biologos said:
I would really appreciate it if anyone knows which app(s) is/are responsible for this.
Click to expand...
Click to collapse
Ideally, you should post all the apps you've installed so anyone coming across this thread can scan what you have and have the chance to see an app that is knowingly bad.
You should always restore to a factory state to make sure it *is* a bad app though. That's the only way to verify if it's Honeycomb or a tablet hardware issue as being the cause rather than a rogue application.
Also, don't install *questionable* apps from *shady* sources. Eventually, this kind of thing will happen.
Well, I have installed lots of free apps, so it would take a while to post them all here. I have removed a few but it didn't help. It could be anything, of course, but I suspect it must be one that has root access. When I tried freezing a few likely culprits, it didn't change anything though.
Do you by any chance use morelocale 2?
I had some force closes and it was because my tablet was using a language that it didn't like (together with my Contacts) so I had to change some settings (use different locale or delete any custom characters from my contact list) and it worked.
I have the same problem. I restored apps from the android market because I couldn't figure out how to make market enabler work in the beginning. Ever since all the native apps are force-closing.
Sent from my GT-P1000 using XDA App
bpivk said:
Do you by any chance use morelocale 2?
I had some force closes and it was because my tablet was using a language that it didn't like (together with my Contacts) so I had to change some settings (use different locale or delete any custom characters from my contact list) and it worked.
Click to expand...
Click to collapse
I have removed morelocale2 and the problem persists. However, Even after removing it, the added localisations seem to persist (for example, market is still translated to greek). Does anybody know of a method to completely remove its effects?
Removing locale won't disable it's effects. You can set it and them remove it and the settings will remain as you've set it.
You should reinstall it and then set it back to default settings and see if that helps you problem. My problem was an unsupported language that I've set in it and that caused crashes.
I redownloaded it and reset the settings to English (US). When I did that, the apinap force close message reappeared, so there must be some connection. Then, to make sure, I rebooted and tried the apps. Even though the new/old localisation was working as expected, the acer apps still force close, giving the same error as before.
Odd. Did you enter the info (in morelocale) manually or did you use the two selection buttons and pick the language from there?
I just picked it from the selection list.
Then it's not the same as my problem. But I still suspect that it has something to do with locale.
Do you have any custom characters under your contacts. Because that can cause problems (I've stumbled upon it when I was looking if anyone is experiencing the same crashes as I was).
If you do have them (any greek lethers and such) then try disabling google sync and wiping contacts and see if that helps. If it does than it's your contacts (some people reported that some unsupported characters and multiple notes could cause crashes on tablets).
If it still crashes then just enable sync again and restore the contacts.
I don't know what else you could do if you still experience crashes after that except a hard reset to check if that helps.
Thanks mate, I tried this too. In fact, I also removed everything with any Greek character at all. No luck at all, so I will give it a rest. I will just keep the apps in case they are needed for the 3.1 update.
I never used titanium backup, but if anyone is restoring a full backup set from this application and any honeycomb only settings gets deleted or written over by 2.2 information, you will probably have a crash..
just like flash 10.3 has 2 different libraries loaded, one for 2.2 and one for 3.0 , but only installed one of them, your device with flash will FC, when flash suddenly uses 2.2 libraries.. so not all backups and apps can be easily restored..
you will need to test the apps backed up, and avoid restoring any system settings.
This may seem dumb to people who know a lot more about development than I do, but I had an issue that I was having a hard time with and came up with a solution that worked. So, I wanted to share it in case anyone else has the problem.
Background: My phone was rooted. I had side loaded some apps including my favorite keyboard that I use on my Galaxy S called TouchPal. There is a whole thread on installing alternative keyboards in the development section.
After I side loaded TouchPal and followed the instructions in the alternative keyboard thread, I was getting consistent FCs and system dumps. My KF wouldn't let me do anything for more than a few seconds without FC and system dump. The system dump is what was really killing me. I couldn't access anything because the device kept going back to the dump after every FC.
I went to different threads and was trying to do some things like unbrick or uninstall the app through adb. But I am too dumb to follow the instructions precisely so in desperation I wondered if I could do anything in those few precious seconds I had when the device was not experiencing a FC.
Now, during this process below I was constantly having to continue after a Force Close until I could do it fast enough that the device didn't have time to FC before I had completed the process. It's seems very simple, but it did work and you have to be quick:
1. Hit the quick menu
2. Hit "More"
3. Hit "Device"
4. Hit "Reset to Factory Defaults"
After I did this, the device started to go back to a default state even though I was continuing to get FC as the device was doing this.
Eventually it was able to complete and the device rebooted. After it was done booting, I was still getting FC from the TouchPad keyboard, but I wasn't getting the system dumps, which is what really prevented me from doing anything. Finally, I was able to get to my applications and "Force Stop" the TouchPal keyboard. Then I was able to remove it.
My situation may be unique, but I hope it helps someone.
In recent weeks, I have started seeing this pop-up on an annoyingly frequent basis... like every 20-40 mins or so:
An unexpected error has occurred requiring the app to close. An crash report has been sent to the developer to help fix the issue.
Click to expand...
Click to collapse
That's all. No mention of what app. It happens seemingly randomly while I am doing various things: browsing, chatting, looking at a map, reading news, taking pictures, looking at pictures, etc.
I have no idea what is causing this. Given it happens while doing many different things, it seems likely it is a background app or system service that is going wrong. But what? I am guessing this started 4-6 weeks ago. In that time, I have had a Samsung system update, I installed all the various app updates that have become available, and I have probably disabled what I deem as unnecessary permissions for many apps, possibly having disabled one or more permissions that are actually needed.
I am happy to revert permissions, but where to start? Anyone know what app or library produces this anonymous message?
Yes, I googled this error. The only other place I find it is in a report to a Verizon forum, with no useful help.
Phone is SM-935FD, stock Samsung firmware, up-to-date, not rooted. Because it is not rooted, a logcat program hasn't been much help. What other info can I provide, anything else I can do to debug this?
Reporting back that this seems to have been caused by insufficient permissions on the Google Play Services system app. Having turned those permissions all back on again, this error has stopped occurring.