I always build my app choosing with 'Build and run' (not 'build and debug'). While the app running smoothly I opt to put a breakpoint over a line. When I do this the simulated application suddenly quits with a message 'Loading debugger..,Debugging terminated'.
...Actually, this happens only on putting breakpoint on first time.
Any help, please.
Xcode consol log..
Session started at 2010-03-31 20:54:59 +0530.]
GNU gdb 6.3.50-20050815 (Apple version gdb-1461.2) (Fri Mar 5 04:43:10 UTC 2010)
...
This GDB was configured as "x86_64-apple-darwin".A0:0
..
Attaching to process 10016.
Pending breakpoint 1 - ""XXX.mm":247" resolved
Current language: auto; currently objective-c++
sharedlibrary apply-load-rules all
Loading program into debugger…
Pending breakpoint 1 - ""XXX":247" resolved
kill
consol app log....
31/03/10 8:55:02 PM com.apple.launchd.peruser.502[94] (UIKitApplication:com.xxxx.yyyyy[0x25ab][10016]) Exited: Killed
31/03/10 8:55:02 PM SpringBoard[10014] Application 'XXXXXX' exited abnormally with signal 9: Killed
31/03/10 8:55:02 PM SpringBoard[10014] Unable to create CFServerConnection. Telephony state may be incorrect.
Do you have a second monitor connected to your development machine ? If so, try unplugging it and see if that helps. Seriously: http://support.appcelerator.net/discussions/support/572-iphone-simulator-shows-no-windows
I have very similar experience, rebuilding your application will fix the issue.
If it is still crashing try to crack the crash report http://www.anoshkin.net/blog/2008/09/09/iphone-crash-logs/
There is similar topic discussed in another forum go through this http://forums.macrumors.com/showthread.php?t=474267
Related
I successfully got a Today widget working in my iOS app. It works great when running the widget on the simulator or running on a device from Xcode. But it doesn't update if I install the app on a device and then run the widget (not from Xcode).
Has anyone else faced this issue? Is there a fix to this or is this a known bug? Any workarounds so I can have a bunch of beta testers check the app using Testflight and get the widget to work?
Using Xcode version 6.1.
Adding log statements tells me that all the correct methods are called. But after that a crash log is generated and the logs are very cryptic. This is what the console says
Dec 1 19:23:06 MyDevice ReportCrash[3592] <Error>: task_set_exception_ports(B07, 400, D03, 0, 0) failed with error (4: (os/kern) invalid argument)
Dec 1 19:23:06 MyDevice ReportCrash[3592] <Notice>: ReportCrash acting against PID 3591
Dec 1 19:23:06 MyDevice ReportCrash[3592] <Notice>: Formulating crash report for process MyTest[3591]
Dec 1 19:23:06 MyDevice SpringBoard[48] <Warning>: plugin com.testsaga.MyTest-Today interrupted
And a device log generated during this time lists this statement (specific to my widget - there are other processes in there as well)
Processes Name | <UUID> | CPU Time| rpages| purgeable| recent_max| lifetime_max| fds | [reason] | (state)
MyTest <84554d9818fe3e1fafa848c3fe6a34d5> 1.459 4132 0 - 8076 50 [per-process-limit] (frontmost)
Any insights? Thanks.
**I tried the answer here but it doesn't work for me.
I am getting this error while running in device.
Couldn't register com.xxxx.appname with the bootstrap server.
Error: unknown error code.
This generally means that another instance of this process was already running or is hung in the debugger.Program received signal: “SIGABRT”.
Now i rectified this problem .I have posted answer also if anyone got this error follow my post..
Try this,
Deleteing the app, restarting Xcode, clean build, didn't do anything
--> restart your computer
--> restart the phone
I have released two versions of my App successfully
But after third version of app is released in App Store,when i downloaded from Appstore The App is getting Crashed :
When i try to launch app it is getting crashed immediately, and no crash reports were generated in Xcode Organizer.
The Same app is Working fine in IPAD/IPHONE SIMULATORS 5.0 and 4.1 versions
and also working fine when tested in IPHONE and IPAD devices with IOS 5.1.1 installed(run through XCODE).
No Major changes are given other than some image changes and Animation changes which are working fine when locally tested.
Please find below logs, please help to resolve this issue.
Jul 5 12:16:01 unknown fairplayd.N90[41] : libMobileGestalt computeUniqueDeviceID: total time for bb to return imei: 0 Jul 5
12:16:01 unknown SpringBoard[52] : Unable to obtain a task
name port right for pid 225: (os/kern) failure Jul 5 12:16:01 unknown
com.apple.launchd[1] :
(UIKitApplication:com.myCompany.myApp[0xdaa7]) Exited: Killed: 9 Jul
5 12:16:01 unknown com.apple.launchd[1] :
(UIKitApplication:com.myCompany.myApp[0xdaa7]) Throttling respawn:
Will start in 2147483647 seconds Jul 5 12:16:01 unknown
SpringBoard[52] : Application 'myApp' exited abnormally with
signal 9: Killed: 9 Jul 5 12:16:02 unknown kernel[0] :
AppleFairplayTextCrypterSession::fairplayOpen() failed, error -42110
Actually, this is not your fault. The App Store(s) has been having trouble as of late because it is serving corrupted binaries to consumers. Contact apple through iTunes connect for resolution, or wait a few days and release an update. To all developers reading this with pending application updates:
Wait, please wait!
Other symptoms of this include:
The app crashes immediately on launch (not even a splash screen shows, just black->crash).
Affected consumers are spread across many regions (not localized), but some are unaffected.
Your app/update has been approved fairly recently.
Mac apps will show "[App] is damaged and can't be opened. Delete [App] and download it again from the App Store."
The console will print: AppleFairplayTextCrypterSession::fairplayOopen() failed, error -42110
The only fix is to delete the app and reinstall (and basically pray for a working copy). Be assured, you are not the only one! Many major apps from huge companies are being affected by this issue (Angry Birds, NOOOOO).
Corroborated by:
http://www.marco.org/2012/07/04/app-store-corrupt-binaries
http://www.appleinsider.com/articles/12/07/04/developers_suspect_app_store_mix_up_led_to_corrupt_binaries.html
http://www.imore.com/2012/07/04/newly-installed-updated-apps-reportedly-crashing-launch-due-corrupt-app-store-binary-bug/
http://www.forbes.com/sites/anthonykosner/2012/07/05/apple-app-store-encryption-glitch-causes-many-new-app-updates-to-crash-see-list/
In your Locally tested Application Please Remove it in your Device
.After u update or download your updated app in App store
I have no control over the builds. I dont have an apple dev account either. I can use a debug/checked/release build. When running test automation I continue to run into this error: Target failed to run : Remote exception encountered : 'Failed to get task for pid 506'
The automation starts, the application opens and then promptly closes. here is some console output
Oct 25 09:46:48 iphone com.apple.launchd[1] (UIKitApplication:com.something.dogfood[0xd456][504]) : (UIKitApplication:com.something.dogfood[0xd456]) Exited: Killed: 9
Oct 25 09:46:48 iphone SpringBoard[29] : Application 'MyApplicaton' exited abnormally with signal 9: Killed: 9
Any suggestions?
Instruments basically does its work by becoming the debugger for the app. Sometimes after using XCode to debug apps, I find I can't use Instruments until I reboot the device.
Unlike XCode, Instruments can be confused between two apps with the same name, but different bundle IDs. (Or perhaps same name and similar bundle IDs.) When I have multiple versions of an app on a device, I often have to delete the extra to get Instruments to connect to the correct app.
So, delete any duplicates of your app and restart the device.
I am testing an EXE_BAD_ACCESS error. I have set NSZombieEnabled, MallocStackLogging, MallocStackLoggingNoCompact to YES. now in the debugger I get this message when I run my app in the debug mode from the device I could see this:
iota(3586) malloc: recording malloc stacks to disk using standard recorder
iota(3586) malloc: stack logs being written into /private/var/mobile/Applications/8E21A85B-369E-4487-962B-1550E56602DC/tmp/stack-logs.3586.iota.index
iota(3586) malloc: Please issue: cp /private/var/mobile/Applications/8E21A85B-369E-4487-962B-1550E56602DC/tmp/stack-logs.3586.iota.suRQjy.link /tmp/
and when I am about to hit the error I get,
2011-02-14 14:29:44.350 iota[3586:307] *** -[CFString autorelease]: message sent to deallocated instance 0x81eab70
Finally when I give the command in debugger to see the stack trace
(gdb) shell malloc_history 3586 0x81eab70
I get
malloc_history cannot examine process 3586 because the process does not exist.
Can anyone tell me what I am doing wrong, before the error is about the occur , I set
set env MallocStackLogging 1 in the debugger too
Thanks in Advance
You might not be able to look at the malloc_history because you're running this on the device. I had the same error and Instruments was also freezing or not starting my application.
But - if I ran in the iOS simulator and then configured the allocations tool to handle zombies (this option wasn't available on the device) then I can see pretty quickly the object which was prematurely released.
From what I understand you are releasing manually a string that is already on the autorelease Pool.
All strings created with
[NSString stringWithFormat:#"some %#", #"text"];
And
[NSString stringWithString:#"some text"];
must not be manually released.