-
Notifications
You must be signed in to change notification settings - Fork 11
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
Unexpected end of file #34
Comments
Hi @minotaurrr, I've tried replicating the issue with your app (I'm an Admin on the Shoutem Builder, so I'm able to do so, other users can't clone other's' apps). I was unable to reproduce the issue. This may be an issue with npm, check this issue for more information. My environment: |
I m getting same error. |
@minotaurrr Did you solve your problem ? |
I m getting same error too. |
Please solve this issue |
I am getting same error. Node: 8.9.4 |
Also getting the same error ! Any solutions ? |
Hey everyone. Can you please provide your environment details so I can attempt to reproduce the issue? Looking at other people's reports regarding this, the issue is often tied to an unstable or otherwise unusual internet connection. It's possible that proxies, VPNs or simply a poor connection may be causing issues when attempting to download the issue. Apparently, Nodejs versions 4.6.0 and 7.X.X help resolve the issue in most cases as well. |
Mine is now resolved. I updated CLI. its seems ok. I m using node 8.9.4 |
@Vladimir-Vdovic Shoutem CLI :
$ node -v $ npm -v Windows 8, 64 Bit. Error : Use shoutem last-error for more info $ shoutem last-error If you think this error is caused by bug in the shoutem command, you can report the issue here: https://github.com/shoutem/cli/issues |
@nazrdogan Which shoutem cli version you are using ? |
Mine issue resolved now. I downgraded my node version to 7.x.x and it is working fine now. |
@atulquest93 Downgrade your node version to 7.x.x and it will work. |
@atulquest93 I m using . 0.10.9 |
node v- 8.9.4 arch -64 bit on windows v- 10 arch -64 bit Pro shoutem-cli v -0.10.9 |
getting the same error with node v7.10.0, v8.9.4 LTS |
it don`t work with node v7.10.1,npm v4.2.0 macOS v10.13.2 |
Still getting this error with
as @Vladimir-Vdovic commented. macOS 10.12.6 Is anyone working on this issue? Thanks! |
Me too, same issue:
|
Sorry for the long wait, everyone, I hope we'll be able to fix this soon. We've released a new beta version on npm - it does not fix the issue, but it should provide clearer HTTP and unzip errors. Please install it ( Thank you for your patience. |
We've published a new beta to npm today (v0.11.0-beta5). After spending some time reading about zlib errors and trying to replicate this particular error*, we've decided to do the following if a Z_BUF_ERROR is encountered when unpacking tgz archives:
There's always the possibility that this is a non-fatal error (https://zlib.net/zlib_faq.html#faq05) and the process might be able to continue, but that's hard to determine without more information. Therefore, we'll look into implementing checksums so we can be certain of a downloaded file's integrity. * the results were inconsistent. We've encountered the error once when running shoutem clone, and everything went fine a minute later when retrying the same command. So, it's probably safe to say that the error is somewhere in the network transfer. |
It is not working on windows 8, 10 but it is working in mac os |
$uname -a //MacOS High Sierra; 10.13.2 (17C88) $ node -v $ npm -v $ shoutem -v shoutem last-error If you think this error is caused by bug in the shoutem command, you can report the issue here: https://github.com/shoutem/cli/issues |
It worked after I deleted .shoutem folder from user home $rm -rf ~/.shoutem |
Hi guys,
I'm getting this error when I run
shoutem clone
Tried
brew update
but didn't help. Anyone with a similar experience?The text was updated successfully, but these errors were encountered: