i am developing drawing application in ios. i am touchesmoved event continuos execute after some times crashed my application.but,it's not show error message console and shows (gdb) in console and project is running state it's shows by thread is paused.i am not bookmark statement's at any point..!
My state below screen shot
Try Enabling NSZombie
It May Be EXE_BAD_EXCESS.
You can check how to enable zombie and many more to resolve crash issue in your application from the Following Link
http://www.raywenderlich.com/10209/my-app-crashed-now-what-part-1
2.https://stackoverflow.com/a/4917557/730776
Regards
Neil
Is your app launching (maybe with a black screen) at simulator/device launched? In short whats the device state. In my case it was not able to find the SDK and there was a popup in simulator window, which somehow got hidden and I was clueless for some time.
Related
I have a problem with Xcode 4.4.1 .
My Simulator becomes translucent black and hangs without any proper log message when I pressed a login button of my application after app launch.
Sometimes application or Simulator hangs just after the launch when I pressed the button or Sometimes it hangs after few second I request a network call with in application.
No pattern .. no message to trace. Tried many things like Xcode restart ,System restart and Clear logs and deleting temporary iPhone Simulator files in Library like that .
I am not able to get what is happening . Does anyone suggest me solution to get out of this.
Or Does somebody know the reason why this is happening. I mean its the application problem i.e in code or the Xcode or iPhone Simulator App problem.
Any help would be really appreciated.
I faced the same problem last day. I got it working after I have done the following, not sure which step did the trick.
Reset the simulator contents.
Quit simulator
Delete derived data of the project from xcode.
Restart xcode.
When I close my app (double tap home button and touch the X) on my iPhone, it crashes and I get this error:
objc[9337]: class `ADManager' not linked into application
objc[9337]: class `ADSessionManager' not linked into application
objc[9337]: class `ADSession' not linked into application
(lldb)
-Deployment target: iOS 5.1
-Iphone iOS 5.1.1
-Testing with Xcode on iPhone
How can I fix it?
This is the default behavior of all iOS apps in iOS4 and later.
Um, it's not a good idea to be running the app connected to Xcode debugger and then terminate it in the middle of the process. It can very easily lead to the bootstrap error.
The debugger is constantly monitoring your app when you run it in iTunes, terminating it would obviously cause a crash =/
You can see a spinning icon in the "debug" tab in Xcode 4 (the tab with the icon that looks like a speech button and some lines in it in your project navigator) when you're in the middle of debugging.
Not sure what you're trying to achieve by terminating your app, a registered background process such as location service?
I am writing an iPad app and I would like to use Xcode Instruments to see if my app has any memory leaks. I have used Instruments successfully before but with Xcode 4.0.2 recently with this app I have the problem described in the title. It only works very rarely.
Steps to use Instruments:
- From the Xcode menu: Product>Profile
- Choose the Leaks instument
- Watch Instruments start recording allocations and leaks while the app shows its splash screen.
- The app's initial view controller becomes visible and Instruments stops recording at the same time.
Am I doing something wrong? Is this a bug in Instruments?
Any help would be appreciated.
Edit:
Instruments works on the iPad simulator but not the device (iPad 2)
Have you tried changing the profile build from Release to Debug (go into "Edit Schemes" and you can change it there for Profiling)?
It could be something in the release build is causing Instruments to disconnect.
Also, pull up the device console in Organizer while it is running, and see if you see any messages related to the detachment.
Be sure, you device is turned on (in some cases it can be spontaneously shut down).
My app works fine on iOS 3.3, but after I upgraded my iPhone to iOS 4.2.1, I started to see some weird behaviour.
When I start my app on the upgraded iPhone, it goes blank. I have to tap the Home button to close the app.
The problem is, the app did not crash. It just showed me a blank screen. So I don't have any crash report to track this issue down.
Has anyone seen this before? Is it an iOS 4.2-specific issue? What steps can I take to determine the cause so that I can fix my code?
The behaviour of iOS did change between iOS3 and iOS4. As a first step, try walking through your code with the debugger. Also check your application:didFinishLaunchingWithOptions: method in your main App Delegate class.
A quick search also turned up some useful info about a similar issue: App shows white screen on startup after upgrading to iOS 4.2
The link also has info on how they managed to find out what was happening.
I'm having some strange behaviour ocurring when I try to run my Iphone app without using Xcode. If I run it by choosing Build & Run in Xcode it runs just fine, but if I do it by disconnecting the USB cable and tapping on the app on the Iphone, it crashes, yielding an unhelpful crash log.
Is there any difference between these 2 scenarios that could be causing this behaviour?
The difference is that if you run it via Xcode, the debugger is attached and a lot of restrictions are not applied. For example, if an app starts up it must respond with a few seconds otherwise it's killed. If you run it with the debugger, that restriction is lifted. Same when exiting: if you hit the home button (on iOS < 4 or iOS >= 4 without multitasking) then an app gets five seconds to exit. Not so with the debugger attached.
It might help if you post the error message from the crash log.
After having run the app out of XCode, have you terminated it? With iOS 4 it will continue to run in the background, and when you tap on the app on the iPhone, it just brought to the foreground.
Double click on the home button and see if it's still running. If so, tap on the app until the minus sign appears and tap it.