Service exited due to signal: Killed: 9 #1816
Comments
|
From @burkeholland on March 4, 2016 15:33 Updating with possible related race condition error on iOS Simulator. Could be cause by app size. |
|
From @rosen-vladimirov on March 4, 2016 15:35 It looks like there are some problems when deploying application to iOS Simulator related to project's size. Some information can be found here: |
|
From @burkeholland on March 4, 2016 15:56 👍 |
|
From @burkeholland on March 7, 2016 17:45 It appears to me that |
|
From @jlooper on April 4, 2016 15:2 I get this error consistently on iOS emulator when running Angular+{N} apps unless I use the deploy/livesync command above. It's a big workflow stopper for me :(. Hoping to get livesync working for iOS soon as well. |
|
From @tjvantoll on April 15, 2016 19:9 I’m going to open this up, because I know at least @burkeholland, @jlooper, and @sebawita are still having this issue, and I think we need to come up with some way to workaround the problem. |
|
From @tjvantoll on April 22, 2016 12:52 I can confirm that this issue is fixed when using Xcode 7.3 and version 2.0 of the {N} CLI, so I’m going to close this issue for now. If anyone hits this after upgrading to the soon-to-be-released 2.0 CLI please comment so we can look into this. |
|
From @jlooper on April 27, 2016 16:49 I do see this issue if using
|
|
From @georgeedwards on May 1, 2016 14:56 I also face the same issue using 2.0, XCode 7.3 and OSX El Capitan, but it does work with livesync doesn't work for me, so I haven't found a way to get a console.log yet - really annoying However, when running on a real device, the app launches without issue |
|
From @rdlauer on May 9, 2016 20:56 Same issue here with {N} 2.0 + Xcode 7.3.1. The |
|
From @cfjedimaster on June 2, 2016 18:41 I ran into this today. It took me about 10 relaunches or so for it to finally work. I'd seriously consider adding a note someplace in the docs for folks going through the tutorial. |
|
From @tjvantoll on June 3, 2016 13:39 Reopening this because clearly people are still hitting the problem. |
|
From @tjvantoll on June 3, 2016 14:18 @cfjedimaster Warning added in NativeScript/docs@0aebd98. Thanks for the feedback as always. |
|
From @dwehrmann on June 7, 2016 7:24 +1 also having this problem.
jlooper's advice doesn't work for me: |
|
I noticed that manually starting the project via the build xcode project is another way to workaround this inconvenience atm. Do the following: In the terminal execute Its a slower way to run but it deploys 100% of the time. |
|
Ah, It seems that this issue solved from latest In my case, I tried "nativescript": {
"id": "org.nativescript.groceries",
"tns-ios": {
- "version": "2.0.0"
+ "version": "2.1.0"
},
"tns-android": {
- "version": "2.0.0"
+ "version": "2.1.1"
}
},
"dependencies": {
"tns-core-modules": "2.0.0"
...Maybe, "nativescript": {
"id": "org.nativescript.groceries",
"tns-ios": {
- "version": "2.0.0"
+ "version": "2.1.0"
},
"tns-android": {
- "version": "2.0.0"
+ "version": "2.1.1"
}
},
"dependencies": {
- "tns-core-modules": "2.0.0"
+ "tns-core-modules": "^2.1.0"
...Then, |
|
This problem still exists and the issue should be reopened. tns create test-nativescript-angular --ng tns version 2.2.0 |
|
Had the same problem today. I'm unable to init the ios simulator. |
|
Thanks @VladimirAmiorkov that worked. But still, this issue should be reopened, don't you think? Is there a way to use livereload from Xcode? Thanks. |
|
@juanpujol if you mean |
|
Ok, thank you. |
|
I was just having a bunch of trouble with this but this seemed to resolve it. For some reason, it won't allow me to run tns run ios --justlaunch --watchI was able to get this going without having to downgrade any of my dependencies as well. Below are some contents from my "tns-ios": {
"version": "2.2.1"
}
},
"dependencies": {
"@angular/common": "2.0.0-rc.4",
"@angular/compiler": "2.0.0-rc.4",
//other deps
"nativescript-angular": "^0.3.0",
"reflect-metadata": "^0.1.5",
"tns-core-modules": "2.2.1"
}, //.... |
|
Pointed here from groceries tutorial, but can't find the "workaround" tutorial mentioned. At this moment the only way that works is to execute ios app from xcode. |
|
The issue is still there - it happens to me when running the ng-sample project. It does not happen every time and hard to reproduce 100% of the time.
|
|
@thomasjosephgreco thanks! |
|
This is almost certainly memory related. I see this error much more frequently in low memory conditions on my dev machine. |
|
I left a comment on nativescript-angular issue # 101 but looks like it's duplicate from here. I've attacked in so many different ways in order to get the simulator working but no luck so far. |
|
I had the same issue, Service exited due to signal: Killed: 9. I was running MacOs Sierra in Vmware. I was using 4gb of ram and the vm was placed on an normal hard disk. My pc got 16 GB of RAM, when I assigned 8gb to the VM and moved it to my SSD drive, everything was working fine. |
|
I see 2.5 is out, didn't check yet, but I hope this is fixed.. |
|
Still present in 2.5. |
|
Hi ! i have the same issue. I need to restart my imac everytime because of this error. No news about it? |
|
Hey all @nabil-mansouri , @davorpeic If you still encounter this problem could you send us exact steps to reproduce, please. Thanks! |
|
Hi, yes i have the same issue. The whole livesync solution feels fragile and some sort of race condition issue is happening(which I attribute to sometimes it works, sometimes it doesn't). Once in awhile when it fails, I'll see something about hooks an a permission issue (just speculating). When I'm lucky, I don't see this issue, unfortunately, I see it more often than not so rather than fight it, I've come to terms with just using my work around. btw, livesync and --watch are no longer published documented command line options for tns 3.1.3 so don't try those with previously above 2016 mentioned work arounds. For me, this is what I'm having to do. Two different terminals... 1st one to build/deploy/run the code, 2nd one to watch the terminal. Everytime I make a change, I re-run the 1st terminal command again... First Terminal Second Terminal @pkoleva what type of activity and logs can I send you to help give you the "need more info" you are looking for. You're welcome to contact me directly or just ask Jen Looper for my contact info if you like. |
|
Hi @QuinnZillian, If you can isolate the problem, using our latest bits, it will be very helpful for us to have the specific steps to reproduce. You can send us the versions of node and npm you use, what kind of devices or simulators you use to recreate the error, your OS and xCode versions. Also if you could send us the output of Indeed |
|
Hi @pkoleva Here's what you've asked for. Good Luck!!!! Let me know if there is anything else I can provide. Here's a tail snippet of the trace log. The full trace can be found in the trace.zip File contains the trace log and a screen shot of the versions |
|
Hey @QuinnZillian , The problem might occur on iOS 8 simulators (at least according to the same thread) or in case there's some issue in CLI that makes it change the app bundle during launch of application. We have not found such issue in CLI so far, so I assume you were using iOS 8 simulator. Thanks in advance for your help. |
|
Hey guys, Please open a separate issue in case you face the same problem again. |
and others
From @burkeholland on March 4, 2016 14:58
NativeScript Version: 1.6.1
I'm unable to use Angular 2 with NativeScript at the moment. I'm using the
template-hello-world-ngproject.The error I get isn't terribly helpful....
Project successfully built. Using /Users/burkeholland/dev/burkeholland/my-app-name/platforms/ios/build/emulator/myappname.app Starting iOS Simulator Mar 4 08:15:53 --- last message repeated 1 time --- Mar 4 08:15:53 hollandmac com.apple.CoreSimulator.SimDevice.FAE7B936-79CE-46C4-859F-65506A603837.launchd_sim[52478] (UIKitApplication:org.nativescript.myappname[0x71cd][52664]): Service exited due to signal: Killed: 9Steps to recreate:
Copied from original issue: NativeScript/nativescript-angular#101
The text was updated successfully, but these errors were encountered: