I'm not a developper, but a user of an iPhone (3GS, iOS 4.1, Jailbroken) which started to crash randomly last week on several app. If I'm right, it crashes randomly when I tap on the keyboard (texting, sending an email, search on Google...), so that's why the crash happens on several app I guess.
By crashing I mean:
- Either, the app close itself (Safari.app, Mail.app...)
- Or, the SpringBoard crash and the iPhone go on SafeMode
What I did before it started to crash:
- Weeks ago, I installed a Cydia Tweak to setup a Frecnh Keyboard, tweak I uninstalled after it started to crash, thinking it was because of it, but apparently it wasn't
- I installed a .deb manually with Cydia, everything went well
- I modified the /dpkg/status file in order to prevent Cydia from asking me for an app update, everything went well too (besides some description line which I had to delete)
Here are 2 Crash Log:
http://pastie.org/private/nuncku1absv3frk5f4tva
http://pastie.org/private/1lc9lfbhdagkynhsmwm6w
=> They talk about UIKit, does anybody know what is wrong and what should I do to fix the crash? I tried to look for on Google, bu I didn't find anything unfortunately...
Thank you very much for your help!
Thomas
Correct answer:
Get the package "Crashreporter" from Cydia (BigBoss Repo).
For Springboard crashes, you can ignore the warning at first start.
Select the most recent crashlog, wait a moment for the analysis.
The most likely suspect for the crash will be displayed first.
Get rid of that package, and retry.
Related
I am new to iOS development. I was opening the .xib file in the editor and tried to make an iPad version of the app. I went to File > Make iPad Version. An iPad UI appeared. I closed it and didn't save it.
The problem now is that the app is now crashing when viewed from an iPad.
Thanks!
Here's an official answer or, to be more precise, a couple of useful tips from someone who is also new to ios development (4 months):
First of all, update your xcode version. If you are new, there is absolutely no point in starting with an older version. True, it may have a bit more tutorials but it's not that hard to find stuff for xcode 4. Trust me, been there, done that ;)
Second, if you run your app on a device and it crashes, you will get a crash log. Connect the ipad to your pc and open the organizer window from xcode. There, go to Devices and select the logs for your device. The log will help you detect the cause of your problem.
Third, when you will encounter more problems like this in the future, be more detailed when asking for help on stackoverflaw. Post more info, error logs, print screens, etc. Basically, anything that could help others help you
I have an iPhone app that I'm trying to run on my phone via Xcode.
It installs and runs without an issue
I make a change in the source code (negligible, like an NSLog())
It installs without an issue
Running causes the error:
Error Starting Executable 'myApp'
Don't know how to run. Try "help target".
I uninstall the app, and reboot the phone
It installs and runs without an issue (until I make another change; then I have to repeat this dance)
Needless to say, having to uninstall the app, reboot the phone, and reinitialize the environment (i.e. set prefs) takes an unreasonable amount of time, and is probably indicative of a serious problem. The issue is, the only vague error message I receive gets me nowhere on Google. Where on earth could this issue be coming from?
With some help from #iphonedev, I figured it out. Turns out it's a glitch in iOS 5 beta. The way to fix it is to remove the device from Development Devices, then re-add it.
Yeah just restarting the iPhone with the lock and home buttons fixes this. Had it happen a few times to me
I have an app that I occasionally receive support emails for that say the app crashed on them and won't open up anymore. It shows 'Default.png' then exits. Even when the app is deleted and reinstalled.
-I get no crash reports or memory issues (as reported by itunes connect using reports from a significant sample size >20k downloads)
-I've confirmed it's not limited to a specific model and not caused by jailbroken devices.
-The app doesn't have external dependencies, so why would reinstalling it not fix the problem?
What kind of problems could cause the crashing to go unreported and be persistent?
If you have an uncaught exception handler, depending on what you have in there, you will not get reports written out the same way, or at all, as if you did not have a handler. This will make iTunes think there is not any crash reports at all. Uncaught exception handlers are commonly added as part of analytics frameworks, or third party notification tools.
While this could answer your question, a more reasonable explanation is that the crashing devices just need a device restart.
I think every app developer with a sizable install base has struggled with an issue like this in the past.
Are you using any sort of analytics package, such as Flurry, that helps you report crashes? We used Flurry with much greater success over Apple - Apple won't start reporting crashes to you until you have many -- and "just a few" is never enough.
Additionally, if it shows the default.png and crashes, take a hard look at your start-up code. Are you setting something in NSUserDefaults, that if, corrupted, could cause the app to crash on startup?
Admittedly it is strange that a delete-and-reinstall doesn't do the trick.
The users aren't reporting the error reports to Apple. The crashes could come from any number of sources.
You could walk a user through the process of digging crash reports directly out of iTunes during the next Sync and email them directly to you.
You could try asking a user to delete the app from the device, reboot their device, then have them install the app again after a fresh reboot.
I have an iPhone app that's been in development for about 2 weeks. We recently tried the "release" version of the build on a device, and to our great unhappiness, it crashes in one of the views with an "EXC_BAD_ACCESS".
This crash only occurs on devices, and only in the "release" build. Not only that, but it only happens the first time the app is launched! It is also 100% reproducible.
We have removed the small block of code that deals with data persistence, and have tried re-openning Xcode, cleaning the project, deleting and reinstalling the app, etc., as some other questions suggest.
Do you have any advice for a) what might be causing this problem, and b) how to go about debugging if it only happens in "release"?
Thanks
It turns out there was no problem in the code at all.
The reason it was crashing was that Xcode was trying to attach the debugger to the release build for some reason! We are still trying to figure out why, because we have checked the most obvious places, but I'm sure it won't be too hard to track down.
The build works fine if you install from iTunes or the Xcode organizer instead of building and running from Xcode directly, so it won't affect your end-users at all, as long as you are careful to check for other first-run issues.
We can only guess what the cause might but if it's 100% reproducible, then it should be a good candidate for some fprintf-style debugging.
Figure out the most probable place for the error to occur, and start putting "Got past xxx view initialization" style statements in to start narrowing the problem. It's tedious, but eventually, you'll get there.
In theory fprintf statements could affect the problem. However, it's rare that it does so, so it's a good place to start.
Here's the situation:
-Had a development build of the app we just submitted on my phone, working fine for days (and previous builds worked fine for weeks).
-Yesterday, I touched the app icon, the app launches then crashes out (I wasn't connected to my computer at the time, but if I had to guess, it was around or before when applicationDidFinishLaunching runs). Basically, I briefly see my Default.png, then the app closes. This happens every time I try to run it.
-I restart my phone. No difference, the app is still failing to launch. All other iphone apps I have appear to be working fine.
-This morning I reinstall the app from my development computer and all is well, it's working fine again. No problems. This is the SAME EXACT CODE with the same build parameters.
This has me really worried, does anyone have any idea at all what might have happened? It's like the app permanently broke itself, before it even hits any of my code no less :(. I had a theory it might have had to do with an expired provisioning profile, but I didn't get any message then or when I reinstalled.
I'd appreciate any advice/pointers/ideas people have!
Connect your iPhone to the computer, launch XCode, go to the Window menu, and select Organizer. Click on your device in the left hand bar, and check your crash logs.
That should tell you when it is crashing, and why.
Actually, the crash logs should still be there from when your app WAS crashing, so even if you have reinstalled, you may be able to figure out what WAS going wrong.
Are you using core data?
Did you change your schema? That would cause a crash on startup and a reinstall would then fix it.
If it was the exact same code it seems to point to a data issue.