Unable to use 'rake device debug=1' since iOS7 Beta 3

Showing 1-4 of 4 messages
Unable to use 'rake device debug=1' since iOS7 Beta 3 sh...@bitspin.org 7/31/13 9:19 AM
Hi,
not sure if anyone is expecting this too or it's something missing on my part but I'm no longer able to debug on-device with iOS7 beta.
I've experienced this since Beta 3 (tbh. I didn't try it with B1/B2) and it still persists in the recent Beta 4.

When I try to run 'rake device debug=1' everything works up to the app being installed on my device 
(it's there and I can actually launch it manually) but then things start to go wrong:

2013-07-31 18:09:39.191 deploy[10188:f07] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'launch path not accessible'
*** First throw call stack:
(
        0   CoreFoundation                      0x00007fff95a8eb06 __exceptionPreprocess + 198
        1   libobjc.A.dylib                     0x00007fff8e22c3f0 objc_exception_throw + 43
        2   CoreFoundation                      0x00007fff95a8e8dc +[NSException raise:format:] + 204
        3   Foundation                          0x00007fff96c50c22 -[NSConcreteTask launchWithDictionary:] + 409
        4   Foundation                          0x00007fff96c5033d +[NSTask launchedTaskWithLaunchPath:arguments:] + 205
        5   deploy                              0x0000000100003511 main + 7793
        6   MobileDevice                        0x00000001005dca16 _AMDDeviceAttachedCallbackv3 + 147
        7   MobileDevice                        0x000000010057888e _USBMuxCustomRunLoopSourcePerformCallback + 1083
        8   CoreFoundation                      0x00007fff95a0db31 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
        9   CoreFoundation                      0x00007fff95a0d455 __CFRunLoopDoSources0 + 245
        10  CoreFoundation                      0x00007fff95a307f5 __CFRunLoopRun + 789
        11  CoreFoundation                      0x00007fff95a300e2 CFRunLoopRunSpecific + 290
        12  Foundation                          0x00007fff96c857ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
        13  Foundation                          0x00007fff96c8569b -[NSRunLoop(NSRunLoop) runUntilDate:] + 78
        14  deploy                              0x0000000100001bb3 main + 1299
        15  deploy                              0x0000000100001694 start + 52
)
libc++abi.dylib: terminate called throwing an exception
rake aborted!
Command failed with status (): [XCODE_DIR="/Applications/Xcode5-DP4.app/Co...]
/Library/RubyMotion/lib/motion/project/template/ios.rb:168:in `block in <top (required)>'
/Users/shirk/.rvm/gems/ruby-1.9.3-p194@StackMotion/bin/ruby_noexec_wrapper:14:in `eval'
/Users/shirk/.rvm/gems/ruby-1.9.3-p194@StackMotion/bin/ruby_noexec_wrapper:14:in `<main>'
Tasks: TOP => device
(See full trace by running task with --trace)

This behavior is 100% reproducible for me so any help is appreciated.

Cheers,
Shirk

Re: Unable to use 'rake device debug=1' since iOS7 Beta 3 Andrew Gertig 8/20/13 5:55 PM
Same problem :(
Re: Unable to use 'rake device debug=1' since iOS7 Beta 3 wndxlori 8/21/13 2:16 PM
Me three.
Re: [RubyMotion] Re: Unable to use 'rake device debug=1' since iOS7 Beta 3 René Köcher 8/21/13 2:48 PM
The problem seems to be lldb.
Apparently Apple dropped gdb in beta3 and RubyMotion as of now doesn't have the tools to run remote lldb.
(rake simulator debug=1 works but uses lldb)

Am 21.08.2013 um 23:16 schrieb wndxlori <javad...@gmail.com>:

--
You received this message because you are subscribed to a topic in the Google Groups "RubyMotion - Ruby for iOS" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rubymotion/8NLSL5ZrUMY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rubymotion+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubymotion/4e3661c1-897f-480e-98c8-64d90319c6b2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.