-
Notifications
You must be signed in to change notification settings - Fork 430
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
Clasp commands return offline error 90% of the time #872
Comments
I have same issue too. % npx clasp push
script.google.com ✖
Error: Looks like you are offline.
% npx clasp push
script.google.com ✖
Error: Looks like you are offline.
% npx clasp push
script.google.com ✖
Error: Looks like you are offline.
% npx clasp push
drive.google.com ✖
script.google.com ✖
Error: Looks like you are offline.
% npx clasp push
script.google.com ✖
Error: Looks like you are offline.
% npx clasp push
script.google.com ✖
Error: Looks like you are offline.
% npx clasp push
script.google.com ✖
Error: Looks like you are offline.
% npx clasp push
drive.google.com ✖
script.google.com ✖
Error: Looks like you are offline.
% npx clasp push
script.google.com ✖
Error: Looks like you are offline.
% npx clasp push
drive.google.com ✖
script.google.com ✖
Error: Looks like you are offline.
^P
% npx clasp push
drive.google.com ✖
script.google.com ✖
Error: Looks like you are offline.
% npx clasp push
...
Pushed 2 files. # On OSX 11.5.2
% node --version
v16.5.0
% npx clasp --version
2.4.1 |
I was seeing this same error when using node version I'm not 100% sure, but could this be specific to the Node 16? |
I have the same issue when using clasp version 2.4.1. But it works well when downgrading to 2.3.1.
|
Downgrading Node to 14.17.5 worked for me as well. |
node v14.17.5 |
node v16.15.0 |
For those looking for a quick way to downgrade clasp:
|
I would remove the feature that checks if you're online on not: Lines 220 to 226 in e851215
|
Any news on that? I am experiencing the issue without any alternative 😢 |
@RealSlimMahdi The combination of node As for the fix, it seems like we are waiting for this PR to be manually merged: #937 @sqrrrl Could you confirm? |
Expected Behavior
No error
Actual Behavior
Almost every time I run a clasp command, I receive this error with one or all of the domains listed
Once in a while the command manages to work successfully, but sometimes I have to retry the command 10+ times.
Steps to Reproduce the Problem
clasp push
orclasp pull
Specifications
node -v
): 16.7.0clasp -v
): 2.4.1The text was updated successfully, but these errors were encountered: