When I implement a new project or update automatically the DataStudio settings in the manifest are deleted.
Does anyone know why this happens?
This seems to be an issue related to Apps Script's new editor.
I suggest you open an issue on Google's Issue Tracker here.
A workaround for this is to switch to the old editor.
+1 I've been having the exact same issue with new UI. I keep switching back to the legacy UI and reverting the Manifests version back.
I think some update must have happened on the backend to cause this but I'm not sure what. Will start using the legacy UI to deploy for now.
In the meantime I've opened this issue with the google issue tracker you linked above
https://issuetracker.google.com/issues/194244611
Related
I have started receiving the message "Unreachable Service - appsactivity" today while executing my google apps script webapp. Anyone knows if there is an outage going on?
Unreachable Service - appsactivity
The previous answer is correct but the issue mentioned is now closed as a duplicate of
https://issuetracker.google.com/issues/169584647
Consider adding a star (on top left) to this issue instead. In addition, a related error:
Service not found: appsactivity v1
is also reported as duplicate of the above issue.
Possible solution(s):
Star the issue to pressure Google into fixing it and wait.
#30 - Remove appsactivity service from manifest file: appsscript.json
#33 - Disable V8 runtime
#43 - Disable, save and re enable Resources > Advanced Google services > Drive and Drive activity api
#49 - Enable the Apps activity api "for the project" you're having issue with.
#53 - Delete current project and create, use a new script
https://issuetracker.google.com/issues/169595450
Reported and assigned to someone at Google. Seems like an outage/unintended change.
This issue seems to be related to the deprecation of Drive Activity API v1. Google recommends migrating to v2 (See here).
You may need to clear caches, and perhaps even reactivate the advanced service.
So I was also facing the same issue.
The issue tracker suggests that it is because of depreciation of Drive V1 Api although when I checked my drive API version it was already the latest one so I tried the following which worked.
Click on View>>show Manifest File to see a JSON file that contains scopes.
and remove Apps Activity scope (I have tested my app in dev mode all things are working I will go through the necessity of this scope later).
it should look like this
{
"userSymbol": "AppsActivity",
"serviceId": "appsactivity",
"version": "v1"
},
I hope this helps you please comment back your response.
Thank You.
The solution it's Disable Runtime V8.
Open the script in the Apps Script editor. Select Run > Disable new Apps Script runtime powered by V8
Thats all
Im fixed my issue
Update: May 2nd 2021:
After a lot of trial and error the solution above to disable the v8 runtime is partially correct and does function -- as long as you don't try to use any other scripts with the V8 runtime as a library.
The complete solution -- You can update individual scripts to V8 but if you have any libraries attached to the script that are not also upgraded to V8 then the script will throw the 'unable to locate appsactivity v1' error.
Updating all of the scripts that are used as libraries to V8 as well was the key to fixing this issue for my scripts.
Frustrating that Google is pushing the upgrade to v8 (disabling debugger, etc...) without first fixing this issue since this is going to really throw some folks (like myself for quite some time) for a loop.
I have started receiving the message "Unreachable Service - appsactivity" today while executing my google apps script webapp. Anyone knows if there is an outage going on?
Unreachable Service - appsactivity
The previous answer is correct but the issue mentioned is now closed as a duplicate of
https://issuetracker.google.com/issues/169584647
Consider adding a star (on top left) to this issue instead. In addition, a related error:
Service not found: appsactivity v1
is also reported as duplicate of the above issue.
Possible solution(s):
Star the issue to pressure Google into fixing it and wait.
#30 - Remove appsactivity service from manifest file: appsscript.json
#33 - Disable V8 runtime
#43 - Disable, save and re enable Resources > Advanced Google services > Drive and Drive activity api
#49 - Enable the Apps activity api "for the project" you're having issue with.
#53 - Delete current project and create, use a new script
https://issuetracker.google.com/issues/169595450
Reported and assigned to someone at Google. Seems like an outage/unintended change.
This issue seems to be related to the deprecation of Drive Activity API v1. Google recommends migrating to v2 (See here).
You may need to clear caches, and perhaps even reactivate the advanced service.
So I was also facing the same issue.
The issue tracker suggests that it is because of depreciation of Drive V1 Api although when I checked my drive API version it was already the latest one so I tried the following which worked.
Click on View>>show Manifest File to see a JSON file that contains scopes.
and remove Apps Activity scope (I have tested my app in dev mode all things are working I will go through the necessity of this scope later).
it should look like this
{
"userSymbol": "AppsActivity",
"serviceId": "appsactivity",
"version": "v1"
},
I hope this helps you please comment back your response.
Thank You.
The solution it's Disable Runtime V8.
Open the script in the Apps Script editor. Select Run > Disable new Apps Script runtime powered by V8
Thats all
Im fixed my issue
Update: May 2nd 2021:
After a lot of trial and error the solution above to disable the v8 runtime is partially correct and does function -- as long as you don't try to use any other scripts with the V8 runtime as a library.
The complete solution -- You can update individual scripts to V8 but if you have any libraries attached to the script that are not also upgraded to V8 then the script will throw the 'unable to locate appsactivity v1' error.
Updating all of the scripts that are used as libraries to V8 as well was the key to fixing this issue for my scripts.
Frustrating that Google is pushing the upgrade to v8 (disabling debugger, etc...) without first fixing this issue since this is going to really throw some folks (like myself for quite some time) for a loop.
I've made some bug fixes to a Google Sheets Add-on and now need to publish those changes. I've created a new version in my Script via File -> Manage versions. When I try to update my Add-on in the G Suite Marketplace SDK I get
Error
Sorry, there’s a problem. If you entered information, check it and try again.
Otherwise, the problem might clear up on its own, so check back later.
Tracking Number: 1747836347906634815
The only change we make is updating the version. This error has persisted for several days now and we really need to push this fix.
Upvote this issue:
Google's issue tracker: https://issuetracker.google.com/issues/150325704
Google Support page: https://support.google.com/a/thread/31561936
I work in the G Suite Marketplace. The issue has been fixed and it's rolling out to production between today and tomorrow.
I've been a passive StackOverflow user for more than a decade now. I don't really think this is the place to ask this but Google Developers Help page referred me here.
Adwords has been updating to a beta version and I'm a heavy user of its Scripts console, but recently, when I want to ad a new script with the big red button, it starts loading and then this message displays: "There was a problem loading the script. Please try again later"
I've already tried with Chrome and Safari, a cookieless browser and with a different account and nothings seems to work. I also Google the error and there is nothing. I don't think I'm the only person experiencing this, do you have any solution?
I couldn't reproduce your problem and was able to create scripts—however, I've noticed quite a lot of bugs in the new web interface (to be fair, they say it's still in beta).
But as a workaround, just use the Return to previous AdWords link in the three dot option menu, which will take you back to the old interface. I could well imagine that you'll be able to add a new script there.
From this morning I have no possibility to edit scripts. My existing script link to a spreadsheet continue to work but when I try to edit them or to edit a new one , I only get a shaded upper bar, and no possibility to use it.
Last times one of my scripts was getting some errors, is it possible that google "ban" me from using script due to too much memory using?
Thanks in advance,
david
I used Chrome Incognito mode as a temporary fix.
Hopefully, this works for you as well.
Switch you drive locale settings to English and it will work. This is a temporary workaround to use until they fix the bug. see issue 4339
Turned out I was still signed into another account despite the UI suggesting otherwise. Restarting the browser and checking who you are logged in as in Drive (and potentially signing the incorrect user out) fixed the problem for me.
Exactly. I was signed with different account without permits. Request access to the Sheet with full access without restrictions and it will work :)