Cannot run livesync with ios simulator

[dharness]

With a new project created with tns create app --ng I am not able to run livesync. Doing so results in the following error:

    Error: EEXIST: file already exists, symlink '../semver/bin/semver' -> '/Users/dharness/Library/Developer/CoreSimulator/Devices/232F86F5-B6C1-44AF-A6D5-2936E8A9EAC4/data/Containers/Bundle/Application/6A27D2A5-3E10-4CF7-8F47-E0857AE3476A/sqwakapp.app/app/tns_modules/nativescript-dev-android-snapshot/node_modules/.bin/semver'

I've tried deleting the simulator, making new projects, restarting the mac.. to no avail.

EDIT:

I have tried without the --ng flag as well with the same result. I have temporarily gone back to 2.3 to generate my project avoid the issue, and am running it using [email protected] cli with no problems.

Of course, i have to temporarily downgrade every time I want to create a new project.

[indrasantosa]

+1 here

[tzraikov]

@dharness and @indrasantosa We addressed the symlink issue with our latest release 2.4.1. Plase, could you confirm that everything is OK when running this version?

[indrasantosa]

Thanks @tzraikov, I have done the fix myself on my local repository, it is now fine :) Cheeer!

[buzzspaceltd]

@dharness @tzraikov I am having the same issue. I just upgraded to 2.4.2 but the issue persists. Any suggestions on a fix?

[indrasantosa]

From what I check, it is due to shelljs copy handles symlink poorly, upgrading shelljs might help, I think

…

On Sat, Dec 24, 2016 at 5:27 PM, buzzspaceltd ***@***.***> wrote: @dharness <https://github.com/dharness> @tzraikov <https://github.com/tzraikov> I am having the same issue. I just upgraded to 2.4.2 but the issue persists. Any suggestions on a fix? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2267 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAadXQVefZmEyEp-AFHuo8kYfjT4cMoLks5rLPOigaJpZM4K9Q34> .

[ludwiktrammer]

I also have the same issue using NativeScript 2.4.2...
I'm using the most recent 0.7.5 version of sheeljs.

[lukeramsden]

I'm still getting this error with the latest version tns update gives me.

[vchimev]

@buzzspaceltd, @ludwiktrammer, @lukeramsden,

Guys, could you please share exact steps to reproduce along with the package.json file of the projects?

I am unable to reproduce such an issue with CLI version 2.4.2. CC: @tzraikov

[lukeramsden]

This is my package.json. What I do is clone the repo, run tns install, then tns run ios --emulator, which works fine, then I run tns livesync ios --emulator --watch and it gives me this error:

EEXIST: file already exists, symlink '../rimraf/bin.js' -> '/Users/*REDACTED*/Library/Developer/CoreSimulator/Devices/CD80306B-7220-4CFD-BA20-026D12FC73C8/data/Containers/Bundle/Application/F9FCCEC9-F518-4CF5-B949-1D75A6B3A675/tissmobile.app/app/tns_modules/nativescript-i18n/node_modules/fs-extra/node_modules/.bin/rimraf'

[vchimev]

Thanks a lot, @lukeramsden! I successfully reproduced the shell.js error you posted.

[vchimev]

@lukeramsden, @buzzspaceltd, @ludwiktrammer,

The issue here is that all .bin directories inside node_modules should be ignored and should not be copied to platforms folder.

A temporary workaround is to remove them manually as follows: find . -iname .bin | xargs rm -rfv

[lukeramsden]

@vchimev Is this going to be fixed in a nativescript-cli updated? Or should I just run this before I try to livesync? For now I'm just gonna make an npm script for this

[vchimev]

@lukeramsden,

it should be enough to run it only once to clean up the .bin directories in node_modules and platforms folders; than use the run and livesync commands with no problem.

We are going to fix it for sure in next minor release (2.5.0) this month along with lots of livesync improvements (#2374); will further investigate if we could provide a patch update (2.4.3) prior that and update this issue if so.

[lukeramsden]

@vchimev My suggestion is a tns clean command. Maybe you could do tns clean node and tns clean platform etc

[vchimev]

This problem does not exist in master branch of NativeScript CLI. It could be installed by:

npm i -g nativescript@next

and it will take part of 2.5.0 official release.