Skip to content
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

"ERROR Error: Could not find module" after 2.5 upgrade #2491

Closed
alexziskind1 opened this issue Feb 6, 2017 · 7 comments
Closed

"ERROR Error: Could not find module" after 2.5 upgrade #2491

alexziskind1 opened this issue Feb 6, 2017 · 7 comments
Assignees
Labels
Milestone

Comments

@alexziskind1
Copy link

The following project throws a seg fault 11 after an upgrade to nativescript 2.5:
https://github.com/alexziskind1/courses-rps-conference-app-ng/tree/master/rps-conf-ng

Here's the full error message:

Feb  5 21:05:55 AlexMBP com.apple.CoreSimulator.SimDevice.7EF5EC7B-FB52-49AF-B710-2077B6F98F98.launchd_sim[15029] (UIKitApplication:org.nativescript.rpsconfng[0xbb3f][16195]): Service exited due to Segmentation fault: 11

This was working well before the upgrade to 2.5 while on 2.4.2.

@Plamen5kov
Copy link
Contributor

Plamen5kov commented Feb 8, 2017

@alexziskind1 Can't reproduce. Ran:

git clone https://github.com/alexziskind1/courses-rps-conference-app-ng.git problem
cd problem && rps-conf-ng
tns run ios

Please provide more detailed information.

@Plamen5kov Plamen5kov added the bug label Feb 8, 2017
@alexziskind1
Copy link
Author

I was just able to reproduce with nativescript 2.5 installed. I recorded a video (about 1.5 minutes) of the process:
https://youtu.be/reeDLOIiSB8

Alex

@Plamen5kov
Copy link
Contributor

@alexziskind1 Thank you, I managed to reproduce your problem, and I will investigate.

@Plamen5kov Plamen5kov self-assigned this Feb 9, 2017
@Plamen5kov
Copy link
Contributor

Plamen5kov commented Feb 9, 2017

@alexziskind1 the missing file is not being copied. This is a problem with a module we're using called shelljs. It's fixed in the next version of the module so we'll try to update and all should be OK. I'll keep you posted.

@alexziskind1
Copy link
Author

alexziskind1 commented Feb 9, 2017

OK Thanks! Is there something I can do in the meantime so I can move past this. Do you suggest a temporary workaround?
It might be easier than what I'm doing now - which is removing everything and installing 2.4.2.

@Plamen5kov
Copy link
Contributor

Plamen5kov commented Feb 9, 2017

You can use cli from @next, because i'll fix it shortly in master branch.
npm install -g nativescript@next

There will soon be a hot fix of cli.

Plamen5kov added a commit that referenced this issue Feb 9, 2017
Plamen5kov added a commit that referenced this issue Feb 9, 2017
This was referenced Feb 9, 2017
@Plamen5kov Plamen5kov added this to the 2.5.1 milestone Feb 9, 2017
Plamen5kov added a commit that referenced this issue Feb 9, 2017
Plamen5kov added a commit that referenced this issue Feb 9, 2017
@pkoleva pkoleva closed this as completed Feb 15, 2017
@alexziskind1
Copy link
Author

Just to give some feedback - using the @next version (3.0.0-2017-02-09-7977) did work.

Thanks for the suggestion @Plamen5kov

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants