Clean exit from a device run about ios-deploy

[shazron]

Can you verify what version of the app where you see this? There have been code updates regarding this issue.

[deanq]

Ok... How? How do you get out of it? The problem here is that after you
deploy, it sticks around into a prompt. I would have to ctrl+c and kill the
process. Is there a quit command I am missing?

On Jul 30, 2014, at 4:56 PM, Shazron Abdullah [email protected]
wrote:

Can you verify what version of the app where you see this? There have been
code updates regarding this issue.

—
Reply to this email directly or view it on GitHub
#38 (comment).

[shazron]

Any version info? There are newer code updates related to device exit that may not require you to kill ios-deploy after ctrl-c. Not sure if it fixes your specific problem exactly, but hopefully. No, no quit command.

[shazron]

Just pushed some newer changes from a contributor's PR #48, related to #11, into the master branch.
From my experience, when you do Ctrl-C, it just exits debugging (and ios-deploy) but you are in the lldb console still. You have to then type in "exit" then enter "Y". I don't see the ios-deploy process still running after that though.

[deanq]

I am using v 1.0.8. So I had a prompt like this:

(lldb)      script fruitstrap_connect_url="connect://127.0.0.1:12345"
(lldb)      command script import "/tmp/fruitstrap_.py"
(lldb)      command script add -f fruitstrap_.connect_command connect
(lldb)      command script add -s asynchronous -f fruitstrap_.run_command run
(lldb)      command script add -s asynchronous -f fruitstrap_.autoexit_command autoexit
(lldb)      connect
(lldb)      run
Process 0 connected
(lldb) ^C%      

Then when I ps aux | grep ios I see two processes that belong to ios-deploy. I have to pkill ios-deploy every time just to get rid of them.

[shazron]

I'm running the latest code from master (unpublished to npm) and here's my output:

$ ios-deploy -d -b Foobar.app
[...]
2014-08-01 15:03:46.936 Foobar[3806:60b] Resetting plugins due to page load.
2014-08-01 15:03:47.335 Foobar[3806:60b] Finished load of: file:///var/mobile/Applications/4CB96B6D-918E-439E-8D48-22E3EA53A3A4/Foobar.app/www/index.html
Process 3806 stopped
* thread #1: tid = 0x1bb7e1, 0x3989ba50 libsystem_kernel.dylib`mach_msg_trap + 20, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
    frame #0: 0x3989ba50 libsystem_kernel.dylib`mach_msg_trap + 20
libsystem_kernel.dylib`mach_msg_trap + 20:
-> 0x3989ba50:  pop    {r4, r5, r6, r8}
   0x3989ba54:  bx     lr

libsystem_kernel.dylib`mach_msg_overwrite_trap:
   0x3989ba58:  mov    r12, sp
   0x3989ba5c:  push   {r4, r5, r6, r8}
(lldb) exit
Quitting LLDB will kill one or more processes. Do you really want to proceed: [Y/n] Y

After that, running ps aux | grep ios doesn't show ios-deploy running.

[deanq]

Looks good! Can't wait until that is released.

[shazron]

Just published 1.0.9 to npm. Release notes: https://github.com/phonegap/ios-deploy/releases/tag/1.0.9

[shazron]

New option in version 1.1.0: --justlaunch

[schmunk42]

Let me just add a finding here I stumbled upon, while having the same issue.

I wasn't able to Ctrl+c + exit + Y until I noticed that I had many many (~20) (ios-deploy) processes running.
So I killed them all with killall ios-deploy and voilà after that, if I start only one process and can correctly shut it down, like described above.

[shazron]

Thanks @schmunk42 - yeah it doesn't clean up from previously.

[deanq]

Yeah, it's still the same old behavior. I still have to kill the process. Is this closed, because it will not be fixed?

[shazron]

No, it is closed because it is fixed as my comments earlier have shown, I can't see any ios-deploy processes after using the latest build.

[albinekb]

Same problem here, running "cordova run ios", unable to exit without killing the process.

[commonpike]

just installed ios-deploy. when doing a 'cordova run ios', it runs on my device. hitting control-c gives

Quitting LLDB will kill one or more processes. Do you really want to proceed: [Y/n] Y

So .. from your comments, I get it this is expected behaviour. Ok.

[venkatpolisetti]

$ionic run ios --device

Just installed latest ios-deploy after upgrading my iPhone 6 to IOS 8.2. I still have to use killall as suggested by @schmunk42 above.

When I do Ctrl+c, it simply exists to the command prompt. If I do exit then, it is logging me out of my terminal session.

What am I missing here?

[joshhunt]

@shazron so iso-deploy now supports the --justlaunch arg to not connect lldb, but cordova run iOS doesn't yet support passing this through. Is that correct?

[senthilmanick]

Hi Josh,
--justlaunch does use lldb but quits cleanly after launching the app.
if --justlaunch is not provided, lldb stays connected to the running app. If you kill lldb (or ios-deploy), then the app will also stop running on the device.
HTH
----- Original Message -----

From: "Josh Hunt" [email protected]
To: "phonegap/ios-deploy" [email protected]
Sent: Friday, March 20, 2015 12:37:11 AM
Subject: Re: [ios-deploy] Clean exit from a device run (#38)

@shazron so iso-deploy now supports the --justlaunch arg to not connect lldb, but cordova run iOS doesn't yet support passing this through. Is that correct?

—
Reply to this email directly or view it on GitHub .

[shazron]

@joshhunt I don't think so, but you can try providing the args after a "--"

cordova run ios -- --justlaunch

(this info was from a cordova help run call)

[raldred]

@shazron thisonly works with the simulator.
If you use with the --device flag it still sits with lldb open.
eg.
I've tried both:
cordova run ios --device -- --justlaunch
cordova run ios -- --justlaunch --device

[shazron]

@raldred can you file an issue to Cordova? http://issues.cordova.io - we're preparing a new release I'd like to investigate this

[raldred]

Thanks @shazron I get a bit overwhelmed with JIRA so hopefully I've reported it correctly.
https://issues.apache.org/jira/browse/CB-9609