Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Clasp push fails silently

See original GitHub issue

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

clasp clone <script ID>
edit script file
clasp push

Specifications

Node version (node -v): v7.5.0
Version (clasp -v): 1.4.0
OS (Mac/Linux/Windows): Mac OS 10.13.3

Issue Analytics

State:
Created 5 years ago
Comments:16 (5 by maintainers)

Top GitHub Comments

2reactions

magerancommented, Mar 4, 2019

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.

2reactions

ikedaosushicommented, Jul 24, 2018

Me too. The same error occurs although the apps script API is enabled.

ADD Now, I updated to clasp@1.5 (before 1.4), it no longer displays the error. However, it takes very long time and not push actually. It display unexpected results as below.

$ clasp push
... (too long)
└─ node_modules/watch/test/test_monitorRootDirectory.js
└─ node_modules/watch/test/test_watchTree.js
└─ node_modules/which/which.js
└─ node_modules/wrappy/wrappy.js
└─ node_modules/yallist/iterator.js
└─ node_modules/yallist/yallist.js
└─ mycode.js