-
-
Notifications
You must be signed in to change notification settings - Fork 197
Livesync hangs, especially bad on iOS #3235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
same issue |
Hey, @vcooley @chauhan-saurabh can you guys test the Please do let me know if you are experiencing the same trouble when using iOS 10 emulators |
I'm still getting the same problem, though so far I have not had multiple incremental compilation messages when I have made no changes. What I am experiencing is the livesync working after multiple changes and multiple saves. So far it has required me to make two changes for the app to refresh. Here's an example of the output where I saved a change, waited ~30 seconds and saved another change.
EDIT: I added a component to my angular application and am seeing my app module and routing file (both of which I modified recently) being transferred multiple times when I make and save changes to other files. |
I was able to reproduce similar issue only on iOS11 simulator with following steps:
|
Hey @NickIliev yes tns run ios (livesync) work fines on iOS 10 |
Hack for iOS11 issue: |
Hi @dtopuzov, Any timeline for fixing this ... pretty much have to kill IOS livesync every one or two changes. Regards, |
Hey @thaoula, |
…ll related processes and services Trying to fix NativeScript/nativescript-cli#3235
Hey guys, I've investigated the issue and found that {N} CLI hangs when trying to start the application. It seems that simctl launch command does not launch the process immediately and we have to wait a little bit, just to ensure all related processes and services are alive. I'm trying to fix the problem with above PR. |
Hi @Fatme, Steps for me are the same.
I have recently switched to @next builds and using tns debug ios --bundle to use the webpack approach which seems much more stable although i cannot debug and it a little slower. Regards, |
Fixed in 4.0rc |
@dtopuzov I am still seeing this issue in 4.0.0. Same steps for reproduction:
The only error message I see in the output is this:
|
Hi @vultix, Execute |
@Fatme I updated to the latest version of XCode and downloaded the IOS 10.3 simulators in my attempts to get debugging working, I'm not sure if that changes the following:
|
Hi @vultix, In case when xCode is updated or new sdk is added, sometimes native build tools are not fully configured and some different errors can happen. Sometimes executing |
@Fatme, Thank you for your help. I am still seeing the same issue. Both on ios 10 and ios 11 simulators. |
Hi @vultix, Sorry to hear that. Another thing you can try is to run your native project from xcode. In case you still have some configuration issue, this should fix it.
After that try to execute |
If the above suggestion does not fix your issue and the error is still reproduced, can you please execute |
@Fatme sorry for the delayed response. I am still seeing the same issue after trying your fix. The build freezes after the Here is the output from the
|
Hi @vultix The original issue is really fixed in 4.0.0 and what you encounter is another issue that result in livesync not working properly. I'm opening the issue again since there is already a lot of communication going here. |
I'm hitting an issue on OS X where the livesync freezes randomly. If I hit Ctrl+C at this point, it seems to unfreeze and gives this error: I have only seen this issue so far on iOS 11, though I haven't tried running on iOS 10. |
Any update on this? I too am getting the same as @EmandM error if I Ctrl+C. If I don't kill the process, it occasionally it freezes referencing an error in Immediate.js, which is needed by rxjs. There is a document.createElement('script') reference on line 56. If I comment out or put an if before it, it doesn't load the updated file, instead the old one before the change. Otherwise it stays frozen on Skipping Prepare |
Same issue. After it happens the only way I found to get it working again is |
This solves but sucks dude! |
When using |
Trying to livesync on an ios device is pretty much impossible I get a successful sync maybe 1 in 10 trys if I'm lucky, not such problems on the simulator. Most of the time it gives a Successfully synced application message even when it hasn't refreshed. The other times it gets to the launch screen and becomes completely stuck. If I try and close the app it just launches itself again and gets stuck at the same place the only thing that can be done is to reboot the device. Seems like removing the platform folder does clear this issue until the next time, but that's not really ideal. |
Hi @dottodot,
|
Closing due to inactivity. |
I'm having multiple issues with livesync, expecially on iOS. I am unsure if they are related, but I will outline what is happening below.
Which platform(s) does your issue occur on?
Both
Please provide the following version numbers that your issue occurs with:
3.3.1
3.3.0
tns-android: 3.3.1
tns-ios: 3.3.0
Please tell us how to recreate the issue in as much detail as possible.
When I
tns run ios
, my app will begin to build and then hang. Building a clean build seems to temporarily fix it, but eventually it happens again, often in the middle of my day when I haven't made any changes to dependencies or anything like that. I have also noticed that when it is hanging I can suspend the app by pressing the home button and it will proceed. I've seen mentioned to run with the--log trace
output and I will paste the content below.At this point, I get a hang and can manually suspend the app to resume. I'd also like to note that if I kill it here I get the following message:
Finally, I'm not sure if this is related or not, but I get many incremental compilation messages when I have made no changes. The app does not refresh after receiving these until I have actually made some changes. For example:
etc...
The text was updated successfully, but these errors were encountered: