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.

Sign up for GitHub

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

Jump to bottom

"tns platform update android" does not work #699

Closed
dtopuzov opened this issue Jul 27, 2015 · 3 comments
Closed

"tns platform update android" does not work #699

dtopuzov opened this issue Jul 27, 2015 · 3 comments
Assignees
@rosen-vladimirov
Labels
bug
Milestone
1.2.2

Comments

@dtopuzov
Copy link
Contributor

Precondition:
npm install -g nativescript@1.1.2
tns create MyApp
tns platform add android@1.1.0 --path MyApp

Steps to reproduce:
npm update -g nativescript
tns platform update android

Result:
ENOENT, scandir 'C:\Users\topuzov\AppData\Roaming\npm-cache\tns-android\1.2.0\package\framework'
@dtopuzov dtopuzov added this to the 1.2.2 milestone Jul 27, 2015
@dtopuzov
Copy link
Contributor Author

Workaround:
tns platform remove android
tns platform add android

@rosen-vladimirov rosen-vladimirov self-assigned this Jul 28, 2015
@rosen-vladimirov
Copy link
Contributor

Unable to reproduce

@rosen-vladimirov
Copy link
Contributor

It looks like the issue is caused by npm cache. It can be reproduced when you manually delete the framework directory under <npm_cache_folder>\tns-android\1.2.0\package

rosen-vladimirov added a commit that referenced this issue Jul 28, 2015
@rosen-vladimirov
Make sure framework dir is part of the cached framework
e681aed 
In some cases framework dir is missing in the npm cached package of the framework. Check if it exists and if not, remove the package from the cache and add it again.
Fixes #699
@rosen-vladimirov rosen-vladimirov mentioned this issue Jul 28, 2015
Closed
rosen-vladimirov added a commit that referenced this issue Jul 28, 2015
@rosen-vladimirov
Make sure framework dir is part of the cached framework
ade93ef 
In some cases framework dir is missing in the npm cached package of the framework. Check if it exists and if not, remove the package from the cache and add it again.
Fixes #699
rosen-vladimirov added a commit that referenced this issue Jul 28, 2015
@rosen-vladimirov
Make sure framework dir is part of the cached framework
506fe60 
In some cases framework dir is missing in the npm cached package of the framework. Check if it exists and if not, remove the package from the cache and add it again.
Fixes #699
@rosen-vladimirov rosen-vladimirov mentioned this issue Jul 28, 2015
Merged
rosen-vladimirov added a commit that referenced this issue Jul 28, 2015
@rosen-vladimirov
Make sure framework dir is part of the cached framework
11e9a59 
In some cases framework dir is missing in the npm cached package of the framework. Check if it exists and if not, remove the package from the cache and add it again.
Fail when the shasum of the package is not correct
Fixes #699
rosen-vladimirov added a commit that referenced this issue Jul 28, 2015
@rosen-vladimirov
Make sure framework dir is part of the cached framework
955f137 
In some cases framework dir is missing in the npm cached package of the framework. Check if it exists and if not, remove the package from the cache and add it again.
Fail when the shasum of the package is not correct
Fixes #699
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rosen-vladimirov rosen-vladimirov

Labels
bug
Projects
None yet
Milestone
1.2.2
Development

No branches or pull requests
2 participants
@dtopuzov @rosen-vladimirov