Clasp push does not update remote code

[klevenick]

Please search existing issues before creating a new one.

DON'T DELETE THIS! FILL THESE SECTIONS OUT!

Expected Behavior

Making a change to the code and pushing it remote, it should update after a push

Actual Behavior

Pushing once does not reflect updated code, it needs a second push to be seen.

Steps to Reproduce the Problem

• Make changes to code.js, save
• Run clasp push, confirms push
• Reload script, change is not seen
• Run clasp push, confirms push
• Reload script, change is seen

Specifications

• Node version (node -v): 11.6.0
• Version (clasp -v): 2.0.1
• OS (Mac/Linux/Windows): OSX 10.12.6

[Cerlancism]

What I believe is the app script's site is not responsive some times(even after refresh) though internally its already updated. My trick is to only leave appscript.json open in the remote site (View -> Show Manifest File). Then use use clasp push. The .gs files should be seem updated this way when clicked on those files.

[grant]

@klevenick It would be useful if you gave me steps in which I can follow to see this problem. This sounds like a pretty critical problem, so I'd expect more people to run into it.

Can you add more details?

[klevenick]

The steps I used to recreate above are pretty much most of it. I tested it from a new project, creating it through clasp and just adding a single line to the Code.js:

var test = "test";

If I make changes locally and push, it takes two attempts for it to be updated on the apps script site's code. @Cerlancism has the trick above that seemed to work, but I wasn't able to produce reliable results, sometimes it seemed like the code reverted after publishing it.

It definitely seems like it only started in the last month, and yeah, I'm not sure why there aren't more reports. I thought it might have been something with my larger project until I started a clean one to test.

[grant]

OK. Maybe it's an issue with 2.0.1.

[murphysprings]

I've seen it on my account and had the exact symptoms described by @klevenick . I had a large project and starting in mid/late December, I pushed updates and the code wouldn't show as updated on the remote side.

clasp push
Go to Google Drive. Open up App Script Project.
Observe that the editor doesn't show updated code in any of the files.
I can't remember if this occurred before or after I updated my clasp install; I had been on an older (maybe 1.4.1) release, then updated to 1.7.0 in December.

I've done the same thing as @klevenick to create this on a new project.

Updated to clasp 2.0.1
clasp create "Test Project"
Copied over some .js files from an old project into the new project directory.
clasp push
Go to Google Drive. Open the App Script Project.
Only see the initial Code.gs file listed; none of my other files.
Even tried a clasp deploy. Opened App Script Project. It shows the deployed version, but no files besides the default Code.gs.

Also tried to eliminate browser issue, thinking it might be UBlock or a privacy setting I have in Chrome. Disabled - no change. Tried the vanilla Microsoft Edge client - same issues seeing the updated files.

Also tried to eliminate settings with my Google account.
Renamed .clasprc.json
clasp login to use different Google account with App Script API enabled
clasp create --title "Test Project" to create project
Copied over one .js file to the new project directory
clasp push
Open Google Drive. Open project. No .js / .gs file present - just the default.

This seems to be some issue with getting the Script Editor to load / reload the code from the updated project.

[murphysprings]

This has been recently reported in the App Script issue tracker:
https://issuetracker.google.com/123311608

[erickoledadevrel]

I've been able to reproduce this behavior and have alerted the internal engineering team. I'm fairly certain that the problem lies in how the Apps Script API interacts with the script editor, so follow that issue tracker for updates.

[autodonncha]

Official Google™ solution: alias clasp pushffs to clasp push && clasp push

[hrzafer]

Official Google™ solution: alias clasp pushffs to clasp push && clasp push

Does that actually work?

[murphysprings]

running 'clasp push' twice in a row just worked for me. It's a workaround.

[murphysprings]

Er, I thought it was a workaround. It doesn't - running push twice still doesn't help.

[Kirandeepv]

@erickoledadevrel Any update on this issue, is the fix expected to come soon ?