clasp: Clasp push fails silently

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

  1. clasp clone <script ID>
  2. edit script file
  3. 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

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 16 (5 by maintainers)

Most upvoted comments

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.

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

@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.