-
Notifications
You must be signed in to change notification settings - Fork 438
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 push fails silently #255
Comments
@paul-matthews check to make sure you've enabled the apps script API? https://script.google.com/home/usersettings I hit the same issue less than 24 hours ago and that was the solution. |
@IanWhalen solved, thank you. Is there any chance this could be caught by the tool and reported? I'll add a FR. |
I have the same error, sadly I already have the apps script API enabled, so that is not a solution for me. |
Me too. The same error occurs although the apps script API is enabled. ADD
|
Hey @ikedaosushi , what does your |
Pushing many, many files could run into unknown issues (although it shouldn't.) |
@jtt48 @ikedaosushi Is this still an issue? Have you been able to ignore the files that you don't want to push? |
Still an issue for me. Same number of files as my last n pushes but for some reason it is no longer working. my ignore file is empty. |
I'm experiencing the same issue. Scripts API is on, and only pushing 4 files.
Pull works fine. Node: 8.11.3 |
Can you provide examples of files that fail to push? |
https://github.com/Blacksmoke16/GESI/tree/master/src/script Ones in this directory. |
@Blacksmoke16
I did use the latest build of clasp (from GitHub), not sure if that makes a difference. |
Yea i don't know what that was about. I installed latest clasp, rm -rf'd the repo directory, recloned it, and it worked. 🤷♂️ |
I've spend a few minutes on this issue today. I can't really reproduce the discussion above: What if the API is not enabled?We report this message if the API is disabled:
What if the API returns an error?If you have a syntax error, we report the error like this:
There's a lot of cases to test. The API reports errors in cases that pushing doesn't work. Also ignoring files may help. I'm going to close this, but please report a new issue if you're still seeing something wrong. |
In my case, the reason for silent failure where backup files left behind by emacs (#somefile.js#). clasp status returned some useful message, which pointed me to that. |
Just had the same problem as mageran, fixed by saving all Emacs buffers related to the clasp project. |
clasp push
fails with no error log:Expected Behavior
After clasp push, expect edits to be present in web interface.
Actual Behavior
Clasp push produces following output:
Push failed. Errors:
No errors are displayed.
Steps to Reproduce the Problem
Specifications
node -v
): v7.5.0clasp -v
): 1.4.0The text was updated successfully, but these errors were encountered: