Obsolete
Status Update
No update yet.
Comments
mu...@gmail.com
I have the same issue. The Script Editor doesn't update the code in the project.
Also being discussed in Clasp project:
https://github.com/google/clasp/issues/507
Also being discussed in Clasp project:
ek...@google.com
Repro:
1) Create a new script using clasp:
$ mkdir test
$ cd test
$ clasp create
2) Locate the script in Drive and open it.
3) Note how the editor shows one file called "Code.gs" with an empty function "myFunction".
4) Add a new local file called "hello.js":
$ echo "function run() { Logger.log('hello world'); }" > hello.js
5) Push the code to Apps Script:
$ clasp push
6) Refresh the script editor.
Expected:
The script editor shows one file calledhello.gs .
Actual:
The script editor still shows only Code.gs.
Notes:
- Refreshing the script editor multiple times over the course of minute doesn't resolve the problem.
- Running clasp push a second time does resolve the problem.
- Further changes to an existing file are reflected in the script editor immediately after clasp push.
- Adding or deleting additional files also results in a stale script editor.
- The stale state applies to the new files and changes to existing files.
- The code is actually updated in the backend, as when you run the code it runs the version you pushed, even though you are looking at the stale version in the script editor.
1) Create a new script using clasp:
$ mkdir test
$ cd test
$ clasp create
2) Locate the script in Drive and open it.
3) Note how the editor shows one file called "Code.gs" with an empty function "myFunction".
4) Add a new local file called "hello.js":
$ echo "function run() { Logger.log('hello world'); }" > hello.js
5) Push the code to Apps Script:
$ clasp push
6) Refresh the script editor.
Expected:
The script editor shows one file called
Actual:
The script editor still shows only Code.gs.
Notes:
- Refreshing the script editor multiple times over the course of minute doesn't resolve the problem.
- Running clasp push a second time does resolve the problem.
- Further changes to an existing file are reflected in the script editor immediately after clasp push.
- Adding or deleting additional files also results in a stale script editor.
- The stale state applies to the new files and changes to existing files.
- The code is actually updated in the backend, as when you run the code it runs the version you pushed, even though you are looking at the stale version in the script editor.
ka...@kobler.no
Same issue here.
aa...@gmail.com
My temporary fix is for each file, go to revision history then revert to the newest version (which should be the clasp pushed version).
iv...@gmail.com
Replicated and following
me...@gmail.com
Please help remove all these hacks i have been stalked n hacked fir 3 years by Luc Savage i even found the facebook hack that has his bike name "karana"in it he has control over all my settings
ek...@google.com
an...@workmanforensics.com
Are there any updates on this issue? I just started using clasp and have yet to have it work successfully, so it could be that I'm doing something wrong, but it appears to be this issue.
- I used
clasp createto create a standalone project - Copied files into the project directory
- Attempted to use
clasp push - Terminal shows a list of files and "Pushed 56 files." so it appears to have been successful
- When I open the GAS project in my browser, only the default Code.gs is there and the manifest has not been updated
edit: I found that in my case the issue was due to a syntax error in one of the pushed files. If I remove that file from the directory, the push is successful.
jo...@google.com
Hi there!
I am currently assessing and researching this issue. If you keep facing the problematic behaviour, write back saying so. If it is possible, please share a script that replicates the issue or the steps required to reproduce it.
mu...@gmail.com
Several of us have documented the steps in the thread
Essentially it is as first described:
- 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
jo...@google.com
Hello!
Thank you for your support. I just forwarded the information to the team in charge for additional analysis.
fa...@gmail.com
Is there a solution for this? It doesn't work for me as well as many people here described
iq...@gmail.com
Is there a solution for this?
ph...@brp.com
Same problem here.
I tried everything suggestion above without any success...
Did you find a workaround?
Thank you.
I tried everything suggestion above without any success...
Did you find a workaround?
Thank you.
lu...@gmail.com
I had the same problem, and I think this is because of an opened tab of your Apps Script project in your browser.
Closing the tab and pushing the code again worked for me.
Does it work for you ?
Closing the tab and pushing the code again worked for me.
Does it work for you ?
vi...@gmail.com
I'm having the same problema here, and I've tried every suggestion without success.
se...@onepeloton.com
Comment has been deleted.
is...@google.com
jp...@google.com
gr...@vida.com
The new editor also has this problem. Is there a new issue?
Description
First, please search through existing issues to ensure that the bug has not already been reported. You can start the search here:
If the issue has already been reported, you can click the star next to the issue number to subscribe and receive updates. We prioritize responding to the issues with the most stars. You can also comment on the issue to provide any details of your experience with it.
If your issue has not been reported, please provide all of the following:
-----------------------------------------------------------------------------------------------------------------------------
A short description of the issue:
when I clasp push to an apps script project, it sometimes takes a few tries until the code in the project updates. I have taken to manually updating a version number in a project file so I can verify that the push worked.
A small code sample that reliably reproduces the issue. The sample should run as-is or with minimal setup, without external dependencies.
this is an intermittent issue with clasp push
What steps will reproduce the problem?
1. clasp push
this is an intermittent problem that can't be reliably reproduced
What is the expected output? What do you see instead? If you see error messages, please provide them.
expected: latest code in the apps script project
actual: not the latest code in the apps script project
Please provide any additional information below.
I have also noticed a change where clasp will accept code with parse errors in it and then the project will break, whereas previously the parse errors would be rejected at the clasp push stage. These two things may or may not be related.