WAI
Status Update
No update yet.
Comments
ja...@google.com
Hello,
Thanks for your report. Unfortunately I cannot reproduce the issue. This message can appear when an external user runs an App or Script with sensitive scopes. Please try to log in from Chrome's Incognito Mode and try again. Also, remove the project's permissions frommyaccount.google.com/permissions .
Cheers!
Thanks for your report. Unfortunately I cannot reproduce the issue. This message can appear when an external user runs an App or Script with sensitive scopes. Please try to log in from Chrome's Incognito Mode and try again. Also, remove the project's permissions from
Cheers!
se...@gmail.com
It's not external; i am trying to run it through the editor.
It's one sensitive scope that I have authorized in another script on the same account.
I tried Icognito and it's the same issue.
The project has no permissions on myaccount page because I can't grant any...
It's one sensitive scope that I have authorized in another script on the same account.
I tried Icognito and it's the same issue.
The project has no permissions on myaccount page because I can't grant any...
ja...@google.com
Thanks for the information. I'm not able to reproduce the issue. Are you using a GCP project to run the script? Can you reproduce this issue in another file?
se...@gmail.com
I am not using a GCP project.
It's just creating a new project in the G Suit Developer Hub; can also navigate to it by pressing the "Start Scripting" button herehttps://www.google.com/script/start/
Which auto creates a new project.
I can reproduce this on all new scripts on my account. If I create a new account it seems to work fine.
It's just creating a new project in the G Suit Developer Hub; can also navigate to it by pressing the "Start Scripting" button here
Which auto creates a new project.
I can reproduce this on all new scripts on my account. If I create a new account it seems to work fine.
ja...@google.com
Thanks for the reply. I need some more information before reporting the bug to the engineers. Please follow the next steps:
1- Open the script in Incognito Mode
2- Press Ctrl+Shift+i and the developer console will show up
3- Reproduce the error
4- In the developer console, click on the Export HAR button (🡇) at the right-top corner.
5- Reply to this thread adding the file as an attachment
1- Open the script in Incognito Mode
2- Press Ctrl+Shift+i and the developer console will show up
3- Reproduce the error
4- In the developer console, click on the Export HAR button (🡇) at the right-top corner.
5- Reply to this thread adding the file as an attachment
or...@gmail.com
See attached.
st...@gmail.com
Hi
I also face the issue, step to reproduce :
1. Create a new script file
2. Copy this code :
function myFunction() {
var url = 'https://google.fr ';
var req = UrlFetchApp.fetch(url);
Logger.log(req.getResponseCode())
}
3. Run the myFunction() function
4. Then you get the pop up error
See error print screen attached.
Stéphane
I also face the issue, step to reproduce :
1. Create a new script file
2. Copy this code :
function myFunction() {
var url = '
var req = UrlFetchApp.fetch(url);
Logger.log(req.getResponseCode())
}
3. Run the myFunction() function
4. Then you get the pop up error
See error print screen attached.
Stéphane
st...@gmail.com
Just tested and the code above works in a G Suite account.
Stéphane
Stéphane
sw...@gmail.com
Same issue, cant create new projects because of this.
Shan
Shan
ma...@eset.com
Same here, can't run new scripts at all.
ja...@google.com
Thanks for your messages. I report the issue to the engineers.
se...@gmail.com
We are having the same issue. It won't authenticate our Google Sheet scripts.
gi...@oogstonline.nl
Same issue here, where old projects will authtenticate just fine but new ones won't. Unless you are using another account (i.e. other than the owner), in which case it will.
aj...@googlemail.com
Same problem for me too. I'm using a consumer Gmail account.
sh...@seatplan.com
Same problem I am having.
All old scripts with URLFetchApp work fine. Any new ones give this authentication problem. Incognito or using other browsers does not help.
As far as I am aware - authentication should only be needed when others are using your published app? But not when the account of the creator is testing and developing?
Previously this has always worked fine for me.
All old scripts with URLFetchApp work fine. Any new ones give this authentication problem. Incognito or using other browsers does not help.
As far as I am aware - authentication should only be needed when others are using your published app? But not when the account of the creator is testing and developing?
Previously this has always worked fine for me.
df...@gmail.com
same issue.
my script works perfectly in 3 different accounts but not in mine!
my script works perfectly in 3 different accounts but not in mine!
ba...@gmail.com
I have the same problem whenever i try to use DriveApp, SpreadsheetApp, DocumentApp, etc. I am using a consumer account on files i own in my drive.
My goal is to open a doc template, copy it, populate from the sheet that contains the script.
This problem did not exist the last time i wrote a script about 2 weeks ago. Old scripts that were previously authenticated and running are still fine.
EDIT: I created a new google account, shared the folder with my new account, and ran the script from the new account. The authorization went as expected and i can run the scripts from the dummy account. HOWEVER, I still can;t run them from my original account because it still tries to authorize and then gives "Sign in temporarily disabled for this App" error.
My goal is to open a doc template, copy it, populate from the sheet that contains the script.
This problem did not exist the last time i wrote a script about 2 weeks ago. Old scripts that were previously authenticated and running are still fine.
EDIT: I created a new google account, shared the folder with my new account, and ran the script from the new account. The authorization went as expected and i can run the scripts from the dummy account. HOWEVER, I still can;t run them from my original account because it still tries to authorize and then gives "Sign in temporarily disabled for this App" error.
st...@gmail.com
same issue here. Old scripts still fine but cannot grant permission to new ones.
so...@telenor.com
Any updates on this? I am not able to authorize any new scripts.
sh...@seatplan.com
For those still having problems - as its been over a month now with no fix in site, I decided to move to AWS Lamdba for the scripts I needed to run.
There is an increased level of complexity with it, but there is also a huge wealth of additional possibilities. It is something I've been meaning to spend some time on investigating for a while, but I'm glad this bug blocking me on Google Scripts forced me into it.
As long as you do not need something to run in Sheets etc it may be worth investigating if you're in a similar position to me and your scripts can be platform agnostic. Lambda is part of AWS's always free version, you are able to edit scripts simply in a web interface and you can code in Node.js which is not disimalar to the setup in Google Scripts.
Hopefully that information is helpful to anyone in a similar situation who has the time to investigate a move!
There is an increased level of complexity with it, but there is also a huge wealth of additional possibilities. It is something I've been meaning to spend some time on investigating for a while, but I'm glad this bug blocking me on Google Scripts forced me into it.
As long as you do not need something to run in Sheets etc it may be worth investigating if you're in a similar position to me and your scripts can be platform agnostic. Lambda is part of AWS's always free version, you are able to edit scripts simply in a web interface and you can code in Node.js which is not disimalar to the setup in Google Scripts.
Hopefully that information is helpful to anyone in a similar situation who has the time to investigate a move!
ha...@gmail.com
Is it possible that this issue is relatable to the fact that I have a google one account with 2T storage?
( my scripts works perfectly with all accounts without subscription plan)
( my scripts works perfectly with all accounts without subscription plan)
ga...@gmail.com
I'm having this problem as well. And I do have a Google One plan on this account...
This is a regular gmail account. This issue does not happen on G Suite accounts.
This is a regular gmail account. This issue does not happen on G Suite accounts.
[Deleted User] <[Deleted User]>
I'm having the same issue since a month ago or so.
Any script that requires authorization, no matter how simple, will fail with the message:
"Sign in with Google temporarily disabled for this app
This app has not yet been verified by Google in order to use Google Sign in."
As an example, running these 2 snippets in the editor will have the following results:
this one runs:
function foo() {
var bar = 1;
}
this does not:
function foo() {
var bar = 1;
var ss = SpreadsheetApp.openByUrl(url);
}
Creating new projects does not resolve the issue.
Any script that requires authorization, no matter how simple, will fail with the message:
"Sign in with Google temporarily disabled for this app
This app has not yet been verified by Google in order to use Google Sign in."
As an example, running these 2 snippets in the editor will have the following results:
this one runs:
function foo() {
var bar = 1;
}
this does not:
function foo() {
var bar = 1;
var ss = SpreadsheetApp.openByUrl(url);
}
Creating new projects does not resolve the issue.
so...@telenor.com
Any news from the engineering team here?
ba...@gmail.com
I have the same issue as everyone else in this thread. One thing that worked for me (at least until this bug gets fixed) was to create another gmail account using a different email. That got rid of the message I was getting preventing me from actually creating/running scripts.
Hopefully this still gets fixed soon, but a new account was a decent workaround the worked for me.
Hopefully this still gets fixed soon, but a new account was a decent workaround the worked for me.
la...@gmail.com
I thought of sharing my experience related to this issue.
I have a spreadsheet with an Apps script. I used to duplicate the spreadsheet whenever I do any modifications to it. But I didn't duplicate recently since the file was not modified. Everything was fine. But several days ago, I had to duplicate it. But this time I can't run the function in the script. Stops with this security error.
FYI: I have a normal consumer Google account.
I have a spreadsheet with an Apps script. I used to duplicate the spreadsheet whenever I do any modifications to it. But I didn't duplicate recently since the file was not modified. Everything was fine. But several days ago, I had to duplicate it. But this time I can't run the function in the script. Stops with this security error.
FYI: I have a normal consumer Google account.
mk...@gmail.com
I'm having the same issue. "Sign in with Google temporarily disabled for this app This app has not been verified yet by Google in order to use Google Sign In."
I just created a simple google apps script on Google Sheet..
I'm the owner of the script. Could you help me please?
I have a normal consumer Google account.
I just created a simple google apps script on Google Sheet..
I'm the owner of the script. Could you help me please?
I have a normal consumer Google account.
ma...@gmail.com
I am encountering the exact same issue as everyone else. Google's sign-in restriction has broken the scripts I have written to generate Google Forms from Google Spreadsheet data. Everything is in the same account and worked fine just a few months ago.
ma...@gmail.com
I have the same issue. I can't use scripting at all :-( Please fix this. Thank you.
ta...@mediacom.com
Broken for me as well.
St...@etxcapital.com
2 months on - can we get an update on where you are at with this please Google? Thanks
la...@gmail.com
Just to give you all an update... It suddenly started working... It
prompted to to pick the user account and after that it complained with a
security message. But I was able to get it through after clicking on
'Advanced' link and then 'Procced...' link
On Tue, Jan 21, 2020 at 9:27 PM <buganizer-system@google.com> wrote:
prompted to to pick the user account and after that it complained with a
security message. But I was able to get it through after clicking on
'Advanced' link and then 'Procced...' link
On Tue, Jan 21, 2020 at 9:27 PM <buganizer-system@google.com> wrote:
[Deleted User] <[Deleted User]>
Quick update:
My scripts can now be authorized again. (tested with thehttps://www.googleapis.com/auth/spreadsheets OAuth Scope)
My scripts can now be authorized again. (tested with the
tk...@gmail.com
Still nothing for me.
sh...@seatplan.com
Also nothing for me sadly :(
aj...@googlemail.com
Works for me again as per post #35 a couple of days ago. Thanks for fixing Google - would be nice though if you could announce it on this issue thread rather than leaving those following the thread to dive in to scripts every day to check if it's fixed.
so...@telenor.com
Still not working for me so i don't think this has actually been resolved
mi...@valkdigital.nl
I am experiencing the same issue.
Using a Google account without gmail.
Trying to run a basic macro recoring in a new sheet and playing it back.
This is my script:
function myFunction() {
var spreadsheet = SpreadsheetApp.getActive();
spreadsheet.getRange('H5').activate();
spreadsheet.getCurrentCell().setValue('sdf');
spreadsheet.getRange('H6').activate();
spreadsheet.getCurrentCell().setValue('sdf');
spreadsheet.getRange('H7').activate();
}
Console is showing this:
1901224078-waffle_js_prod_core.js:4906 [Deprecation] Application Cache API use is deprecated and will be removed in M82, around April 2020. Seehttps://www.chromestatus.com/features/6192449487634432 for more details.
Lbd @ 1901224078-waffle_js_prod_core.js:4906
edit:1 A cookie associated with a cross-site resource athttp://gstatic.com/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032 .
edit:1 A cookie associated with a resource athttp://google.com/ was set with `SameSite=None` but without `Secure`. A future release of Chrome will only deliver cookies marked `SameSite=None` if they are also marked `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5633521622188032 .
accounts.google.com/o/oauth2/postmessageRelay?parent=https%3A%2F%2Fdocs.google.com&jsh=m%3B%2F_%2Fscs%2Fabc-static%2F_%2Fjs%2Fk%3Dgapi.gapi.en.Sj5LKyeUKoE.O%2Fd%3D1%2Fct%3Dzgms%2Frs%3DAHpOoo9ToCtoaz0mr9IKXAop6Eq9AIpSlw%2Fm%3D__features__#rpctoken=299026874&forcesecure=1:1 Refused to load the script 'https://apis.google.com/js/rpc:shindig_random.js?onload=init ' because it violates the following Content Security Policy directive: "script-src 'report-sample' 'nonce-s4UZqbxlhyMLrsi3coWZ6A' 'unsafe-inline' 'strict-dynamic' https: http: 'unsafe-eval'". 'strict-dynamic' is present, so host-based whitelisting is disabled. Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.
clients6.google.com/static/proxy.html?usegapi=1&jsh=m%3B%2F_%2Fscs%2Fabc-static%2F_%2Fjs%2Fk%3Dgapi.gapi.en.Sj5LKyeUKoE.O%2Fd%3D1%2Fct%3Dzgms%2Frs%3DAHpOoo9ToCtoaz0mr9IKXAop6Eq9AIpSlw%2Fm%3D__features__#parent=https%3A%2F%2Fdocs.google.com&rpctoken=369226803:1 Refused to load the script 'https://apis.google.com/js/googleapis.proxy.js?onload=startup ' because it violates the following Content Security Policy directive: "script-src 'report-sample' 'nonce-pHZpmdOvqD79ED4595W+oQ' 'unsafe-inline' 'strict-dynamic' https: http:". 'strict-dynamic' is present, so host-based whitelisting is disabled. Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.
2445743232-waffle_js_prod_ritzmaestro.js:89 Google Apps Script: Authorization is required to perform that action.
edit#gid=0:1 A cookie associated with a cross-site resource athttp://googleusercontent.com/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032 .
2445743232-waffle_js_prod_ritzmaestro.js:89 Google Apps Script: Authorization is required to perform that action.
Using a Google account without gmail.
Trying to run a basic macro recoring in a new sheet and playing it back.
This is my script:
function myFunction() {
var spreadsheet = SpreadsheetApp.getActive();
spreadsheet.getRange('H5').activate();
spreadsheet.getCurrentCell().setValue('sdf');
spreadsheet.getRange('H6').activate();
spreadsheet.getCurrentCell().setValue('sdf');
spreadsheet.getRange('H7').activate();
}
Console is showing this:
1901224078-waffle_js_prod_core.js:4906 [Deprecation] Application Cache API use is deprecated and will be removed in M82, around April 2020. See
Lbd @ 1901224078-waffle_js_prod_core.js:4906
edit:1 A cookie associated with a cross-site resource at
edit:1 A cookie associated with a resource at
2445743232-waffle_js_prod_ritzmaestro.js:89 Google Apps Script: Authorization is required to perform that action.
edit#gid=0:1 A cookie associated with a cross-site resource at
2445743232-waffle_js_prod_ritzmaestro.js:89 Google Apps Script: Authorization is required to perform that action.
ma...@telenor.com
This shit is fu%¤d up. Only getting permission error - cant get authorized. Have to be taken care of! Is this an non-gmail-emails-connected-to-google-account-issue, or does it apply to gmail-account also?
ma...@gmail.com
I am also experiencing this issue and it's been over 2 months now. Hit on both a Gmail account and a GSuite Business account.
kp...@gmail.com
Getting "Sign in with Google temporarily disabled for this app" running Apps Script from script's owner account.
so...@telenor.com
Any updates from Google? Been a few months now
ju...@gmail.com
th...@gmail.com
The same problem. I was running the script owned by me then it stops working by the screen "Sign in with Google temporarily disabled for this app. Sign in with Google temporarily disabled for this app".
That has happened for 3 weeks and still not resolved.
The script works with other accounts.
That has happened for 3 weeks and still not resolved.
The script works with other accounts.
sr...@gmail.com
Same issue here. Existing scripts are working without any issue, new scripts require authorization and hits a dead end at the screen saying - "Sign in with Google temporarily disabled for this app. Sign in with Google temporarily disabled for this app".
I tried creating a script in another account, still no luck.
Its been 15days and we are not able to get it to work, please resolve.
I tried creating a script in another account, still no luck.
Its been 15days and we are not able to get it to work, please resolve.
ic...@gmail.com
Exactly the same issue for me. Cannot run the simplest Google App Scripts in several accounts. Where is the fix for this Google?
sh...@gmail.com
Same here too. Any updates ?
mi...@gmail.com
same for me
ic...@gmail.com
It seems to be spreading to more and more of my accounts. There is no solution I can work out. Please fix.
al...@alsjohnstone.com
Also seeing this issue in a number of accounts.
da...@icrossing.co.uk
Haven't heard anything here from Google in a long time. This completely stops any new scripts running on my accounts and needs to be fixed.
si...@gmail.com
@Google, where is the fix?!
ih...@gmail.com
Commenting here is the same as sending an email to 53 people. Please comment only if you have new information to add. I don't think adding more comments is going to bring more attention, it might just make it more annoying to collect useful information for solving the issue. Another better way might be to ask/help a friend to also star the issue.
fr...@sodimac.cl
Exactly the same issue for me. Cannot run the simplest Google App Scripts in my account. Plz help!
fr...@sodimac.cl
I have a workaround... if you want to run the scripts in an acount that is not a gmail one, just share the doc/sheet to a gmail one with edit permisions, and with in that account run your scripts. Best!
so...@telenor.com
Hi there,
1) i can confirm that it also does effect "business" accounts such as mine.
2) Yes, I was able to run an older script
3) Yes
1) i can confirm that it also does effect "business" accounts such as mine.
2) Yes, I was able to run an older script
3) Yes
ek...@google.com
Thanks for the quick response. Adding another question:
4) Does it happens regardless of the scopes used? For instance, what if you just call UrlFetchApp and nothing else?
4) Does it happens regardless of the scopes used? For instance, what if you just call UrlFetchApp and nothing else?
ve...@icrossing.co.uk
1) I've only this issue only for @gmail accounts so far.
2) Yes scripts already authorized seem to run fine.
3) Yes
4) Yes (see attached)
2) Yes scripts already authorized seem to run fine.
3) Yes
4) Yes (see attached)
we...@tomahawk.nl
Only calling UrlFetchApp results in the same error unfortunately.
ek...@google.com
Thanks for the additional feedback. The team thinks the problem may have something to do with the Cloud Platform projects being used. Can you please address the following questions:
5) When you click "Resources > Cloud platform project", does the dialog say it's an Apps Script-managed project?
6) When you go through the OAuth flow, you should hit a URL like "https://accounts.google.com/signin/oauth/oauthchooseaccount?client_id=.. .". Please copy the client ID from that URL and post it here. It's not a sensitive piece of information and it should allow the engineering team to do more research on the issue.
5) When you click "Resources > Cloud platform project", does the dialog say it's an Apps Script-managed project?
6) When you go through the OAuth flow, you should hit a URL like "
so...@telenor.com
Here's the first message when entering Cloud platform project
Cloud Platform project
This script has an Apps Script–managed Cloud Platform project.
Here's the Client ID from the URL in the authorization
client_id=243491469637-r5ledb23n2v4vnjvn8ui07s1dlq9395k.apps.googleusercontent.com
Cloud Platform project
This script has an Apps Script–managed Cloud Platform project.
Here's the Client ID from the URL in the authorization
client_id=
ma...@eset.com
1) The problem only happens for consumer (@gmail.com ) accounts, correct? - It happens for a "business" account.
2) The problem only happens for new scripts? - Yes. Scripts that have been authorized in the past can be run.
3) The problem happens for every new script? - Yes
4) Does it happens regardless of the scopes used? For instance, what if you just call UrlFetchApp and nothing else? - It happens regardless of the scopes used.
5) When you click "Resources > Cloud platform project", does the dialog say it's an Apps Script-managed project? - Yes
6) client_id=125995377298-dqgq82bhvsf5tdnrj7u7l4cvpmksj3oi.apps.googleusercontent.com
2) The problem only happens for new scripts? - Yes. Scripts that have been authorized in the past can be run.
3) The problem happens for every new script? - Yes
4) Does it happens regardless of the scopes used? For instance, what if you just call UrlFetchApp and nothing else? - It happens regardless of the scopes used.
5) When you click "Resources > Cloud platform project", does the dialog say it's an Apps Script-managed project? - Yes
6) client_id=
da...@icrossing.co.uk
ja...@popken-services.de
Same issue here!
j....@beslist.nl
Same issue here. Please fix!
ja...@gmail.com
Same issue here guys
[Deleted User] <[Deleted User]>
Same issue here
ma...@eset.com
Can we please get a quick fix? I can't be sending automated reports for work from my personal google account :(
ek...@google.com
Thank you for the additional information everyone. The engineering team is still working to find a long-term fix, but we believe we have a workaround that should unblock your scripts. Trying switching the Cloud Platform Project used by your script from a Default Project to a Standard Project, as described here:
https://developers.google.com/apps-script/guides/cloud-platform-projects#standard_cloud_platform_projects
You'll need to do this for each script, which we realize isn't ideal. Let us know if that approach works.
You'll need to do this for each script, which we realize isn't ideal. Let us know if that approach works.
da...@icrossing.co.uk
This is less than ideal but it worked for me as a quick fix.
Thanks!
Thanks!
da...@gmail.com
Same issue here.
ma...@eset.com
Switching to a Standard Project worked for me, thanks.
pe...@gmail.com
Same issue. If the Google Script Project is shared with my other Admins... all admins should be able to use the script! Very pointless decision by google engineers. Will look at cancelling our corp plans.
To be clear of the bug: Owner of the google sheet is person A. Owner of the script project is person B. Both A and B are assigned admins of course! However, only person B is allowed to use the script.
To be clear of the bug: Owner of the google sheet is person A. Owner of the script project is person B. Both A and B are assigned admins of course! However, only person B is allowed to use the script.
fe...@gmail.com
Mee too
ne...@gmail.com
Same issue. This has been opened for five months. I will migrate my work off of Google Sheets moving forward. Personal gmail account, Google One subscriber.
dm...@gmail.com
How has this not been fixed yet? It's basic spreadsheet functionality and is utterly broken. This should be a much higher priority than it apparently is.
be...@gmail.com
I'm also surprised by such broken functionality. Open script editor, type in script, try to run it and get error message. I'm using a personal account -- no cloud or GCP or whatever. It's just me running my own script.
lq...@gmail.com
I have the same problem. Does anyone have an answer?
hy...@gmail.com
+1. Same issue.
an...@gmail.com
Same for me.
kp...@gmail.com
Google, are you kidding me? Development with Apps Script is broken! What's wrong with you
[Deleted User] <[Deleted User]>
Switching to a GCP project worked once out of 3 attempts, and then every user had to be added to the GCP project before they could authorise the script.
This issue should have a higher priority.
This issue should have a higher priority.
pe...@gmail.com
basically this feature does not work. Now if we can't get our scripts
published on the app store... we can't freely use it amongst our own
admin's and google sheets owners.. so bad google, so bad.
*Peter Peng, P.Eng.*
647 588 6623
LucasCreatives.com | Calendly <https://calendly.com/peter-uw/30min >
On Wed, Apr 22, 2020 at 6:18 AM <buganizer-system@google.com> wrote:
published on the app store... we can't freely use it amongst our own
admin's and google sheets owners.. so bad google, so bad.
*Peter Peng, P.Eng.*
647 588 6623
LucasCreatives.com | Calendly <
On Wed, Apr 22, 2020 at 6:18 AM <buganizer-system@google.com> wrote:
da...@gmail.com
I understand that this solution won't work for all cases, but using the
// @OnlyCurrentDoc
scope in the document will allow the script to run. I tried getting permissions, deleting the comment, and running again, but the authorization failed. I also recognize that this won't work for a lot of scripts, but it might keep you afloat until there is an actual solution.
kp...@gmail.com
This stops working as soon as you add changes to your code that requires any new permission. Kind of add to weirdness of this bug.
I understand that this solution won't work for all cases, but using the
// @OnlyCurrentDoc
scope in the document will allow the script to run.
ro...@gmail.com
12345
se...@gmail.com
I have this issue also
pe...@gmail.com
// @OnlyCurrentDoc
did not work for me
did not work for me
da...@gmail.com
If you ask for other permissions that need services from other docs, this
won't work. But if it's self-contained, it seems to work (at least for me).
In the Spirit of Learning,
Dave Ghidiu
On Sun, May 3, 2020, 17:32 <buganizer-system@google.com> wrote:
won't work. But if it's self-contained, it seems to work (at least for me).
In the Spirit of Learning,
Dave Ghidiu
On Sun, May 3, 2020, 17:32 <buganizer-system@google.com> wrote:
hu...@gmail.com
I could not figure out how to switch to a Standard Project, as I don't work in the Google ecosystem much. I got confused and walked away angry.
Please just let my own spreadsheet run my own code. 🤷♂
Please just let my own spreadsheet run my own code. 🤷♂
pe...@gmail.com
This is the top of my script that still doesn't work with @OnlyCurrentDoc:
// @OnlyCurrentDoc
/**
* @OnlyCurrentDoc
*/
//________________
//GLOBALS
//________________
var ui = SpreadsheetApp.getUi();
var ss = SpreadsheetApp.getActiveSpreadsheet(); //get the spreadsheet
var tab = SpreadsheetApp.getActiveSheet(); //get active tab
var selected = tab.getSelection(); //returns a Selection,,, but it can be
non-adjacent... weird!
var selectedRange = selected.getActiveRange();
Also deleted my 1 line of code that uses getURL().
Still doesn't work.
Now if I have to switch to a standard project just for some private scripts
I guess I have no choice lol. Ouch. Missing VBA!
On Sun, May 3, 2020 at 5:46 PM <buganizer-system@google.com> wrote:
// @OnlyCurrentDoc
/**
* @OnlyCurrentDoc
*/
//________________
//GLOBALS
//________________
var ui = SpreadsheetApp.getUi();
var ss = SpreadsheetApp.getActiveSpreadsheet(); //get the spreadsheet
var tab = SpreadsheetApp.getActiveSheet(); //get active tab
var selected = tab.getSelection(); //returns a Selection,,, but it can be
non-adjacent... weird!
var selectedRange = selected.getActiveRange();
Also deleted my 1 line of code that uses getURL().
Still doesn't work.
Now if I have to switch to a standard project just for some private scripts
I guess I have no choice lol. Ouch. Missing VBA!
On Sun, May 3, 2020 at 5:46 PM <buganizer-system@google.com> wrote:
aj...@gmail.com
I noticed this even after I unenrolled from advanced protection. I had to make a new Google Account to work around it.
se...@gmail.com
I tried switching from default to standard project but it would not allow me to proceed without going through OAUTH consent screen, which seems to geared up to approve add-ons and apps, not a sheet bound apps script.
se...@gmail.com
My answers to questions from ek...@google.com at comment 61 62 65:
1) The problem only happens for consumer (@gmail.com ) accounts, correct?
Yes, but not all, for me only the one which happens to have a Google One membership.
2) The problem only happens for new scripts?
Sorry don't know
3) The problem happens for every new script?
No, only the ones containing requests outside the Spreadsheet Service and Script Service it would seem.
4) Does it happens regardless of the scopes used? For instance, what if you just call UrlFetchApp and nothing else?
I tried removing various chunks of codes, and only worked when I removed all the external requests using these scopes:
https://www.googleapis.com/auth/script.external_request
https://www.googleapis.com/auth/script.send_mail
https://www.googleapis.com/auth/drive
It works as normal if only containing these scopes:
https://www.googleapis.com/auth/script.container.ui
https://www.googleapis.com/auth/spreadsheets.currentonly
5) When you click "Resources > Cloud platform project", does the dialog say it's an Apps Script-managed project?
It says: "This script has an Apps Script-managed Cloud Platform project."
6) When you go through the OAuth flow, you should hit a URL like "https://accounts.google.com/signin/oauth/oauthchooseaccount?client_id=.. .". Please copy the client ID from that URL and post it here. It's not a sensitive piece of information and it should allow the engineering team to do more research on the issue.
The client ID is143943784242-u670q2sdvscr613mdc3fo9oj7ug1mqim.apps.googleusercontent.com
I also noticed the subsequent url beginninghttps://accounts.google.com/signin/oauth/danger ? includes a "rapt" parameter which is not included in the url with other accounts which do work.
1) The problem only happens for consumer (@
Yes, but not all, for me only the one which happens to have a Google One membership.
2) The problem only happens for new scripts?
Sorry don't know
3) The problem happens for every new script?
No, only the ones containing requests outside the Spreadsheet Service and Script Service it would seem.
4) Does it happens regardless of the scopes used? For instance, what if you just call UrlFetchApp and nothing else?
I tried removing various chunks of codes, and only worked when I removed all the external requests using these scopes:
It works as normal if only containing these scopes:
5) When you click "Resources > Cloud platform project", does the dialog say it's an Apps Script-managed project?
It says: "This script has an Apps Script-managed Cloud Platform project."
6) When you go through the OAuth flow, you should hit a URL like "
The client ID is
I also noticed the subsequent url beginning
pe...@gmail.com
That's right so it's over kill for what we need. Looks like this issue is not even "high priority" so I'm afraid we do have to reconsider Microsoft for local no hassle sheet projects if this keeps on
Sent from my iPhone
Sent from my iPhone
jg...@gmail.com
Any updates on this? I'm having this on even basic spreadsheets to pull in data from an API and writing the data to a spreadsheet.
to...@gmail.com
Having the same issue. Can't believe this is not fixed for 7 months now
im...@gmail.com
Same issue
se...@gmail.com
re. im...@gmail.com, is your account a 'G Suite', 'Personal' or 'Personal + Google One'?
se...@gmail.com
just tested today, and it's fixed for me, the advanced link is showing, and can now allow scripts in the normal way.
st...@gmail.com
Not for me I tried with a blank script and a call to GmailApp.
Stéphane
Stéphane
la...@gmail.com
I am a coder too.
And I faced the same problem.
In my Google Apps Script, I create a script, and try to `debug` it, then I just grant it with my promission, but after I relogin with grant, it failed. And the page doesn't have any advanced button.
Maybe I am not the only one who faced this issue.
And I faced the same problem.
In my Google Apps Script, I create a script, and try to `debug` it, then I just grant it with my promission, but after I relogin with grant, it failed. And the page doesn't have any advanced button.
Maybe I am not the only one who faced this issue.
ro...@gmail.com
A reply to my ticket 157480303 suggests that I'm a "me too" for this. Though my experience suggests that the problem is (now) with my account, not the script.
Consumer GMail account, struggling with AppScript written in the Script Editor from a Google Sheets document.
I tried to extend my own existing script to use "DriveApp.getFolderById".
Next time I triggered a function, I got challenged to (re-)authorize the script.
Fine. But...
Now, when I "Continue" from the "Auth Required" screen to the list of accounts, and I pick my one (the only option), I get the "Sign in with Google temporarily disabled for this app. This app has not been verified yet by google in order to use Google Sign In".
I have set up a separate GMail account and sent it a link to my spreadsheet-and-script, and that account can authorize it and run functions without problem.
I have also created a copy of a known-good (I can currently run it) version of the spreadsheet-and-script in my own account, and my own account CANNOT authorize it, even though it can still run functions in an identical sheet.
So it looks like my problem is nothing to do with the actual script I'm trying to run, but with my account no longer being unable to authorize anything.
Consumer GMail account, struggling with AppScript written in the Script Editor from a Google Sheets document.
I tried to extend my own existing script to use "DriveApp.getFolderById".
Next time I triggered a function, I got challenged to (re-)authorize the script.
Fine. But...
Now, when I "Continue" from the "Auth Required" screen to the list of accounts, and I pick my one (the only option), I get the "Sign in with Google temporarily disabled for this app. This app has not been verified yet by google in order to use Google Sign In".
I have set up a separate GMail account and sent it a link to my spreadsheet-and-script, and that account can authorize it and run functions without problem.
I have also created a copy of a known-good (I can currently run it) version of the spreadsheet-and-script in my own account, and my own account CANNOT authorize it, even though it can still run functions in an identical sheet.
So it looks like my problem is nothing to do with the actual script I'm trying to run, but with my account no longer being unable to authorize anything.
co...@gmail.com
I'm having this same issue, any update please?
ro...@gmail.com
Update please, indeed.
This problem seriously undermines the value of Google Docs.
An innocuous change to the app I am developing has locked me out of any kind of google Docs extension.
Meaning that if I were using it for anything important, I'd be up a creek without a paddle.
So if someone says to me "I'm thinking of X with Google Docs", what do you think I'll say?
This problem seriously undermines the value of Google Docs.
An innocuous change to the app I am developing has locked me out of any kind of google Docs extension.
Meaning that if I were using it for anything important, I'd be up a creek without a paddle.
So if someone says to me "I'm thinking of X with Google Docs", what do you think I'll say?
pe...@gmail.com
Don't use google docs
Sent from my iPhone
Sent from my iPhone
si...@gmail.com
I have absolutely the same. Nothing helps. Why Google produces service which is impossible to use?
no...@gmail.com
How to fix it?!
ro...@gmail.com
Well, I **WAS** going to say that the only work-around I've found is to create a new google account which I use just for working on my spreadsheet.
BUT... I wanted to remind myself of exactly what the error message was.
So I used my "real" google account to try to open the spreadsheet created by my "hacking" account.
And it opened. And I could run code from the Script Editor.
Without any problem, or even a challenge about wanting to authorize the new sheet.
So it looks like the "temporarily disabled" really was temporary, though nothing notified me of any change.
Not happy....
BUT... I wanted to remind myself of exactly what the error message was.
So I used my "real" google account to try to open the spreadsheet created by my "hacking" account.
And it opened. And I could run code from the Script Editor.
Without any problem, or even a challenge about wanting to authorize the new sheet.
So it looks like the "temporarily disabled" really was temporary, though nothing notified me of any change.
Not happy....
ma...@gmail.com
Trying to run a custom script on my personal account, and I’m hitting this.
It’s a custom one-off AppsScript that is not published anywhere, I just want to run it on my own personal account.
I’ve managed to do this successfully on one other account, so I am pretty sure I am following the steps correctly.
If you need help debugging, or need additional logs, ping me at my corp LDAP, manas@. Thanks!
It’s a custom one-off AppsScript that is not published anywhere, I just want to run it on my own personal account.
I’ve managed to do this successfully on one other account, so I am pretty sure I am following the steps correctly.
If you need help debugging, or need additional logs, ping me at my corp LDAP, manas@. Thanks!
sj...@gmail.com
I also faced the same issue. It started with one script but then affected all scripts, even any brand new ones. One point to note that was using a consumer account (gmail.com ) and had 2 TB purchased storage. However, this error went away on its own in 3-4 days without doing anything from my side. Would suggest that you use an alternate account for a few days. This error will go away on its own.
ep...@gmail.com
I am also getting this message and don't seem to be able to run already existing scripts or new ones.
ep...@gmail.com
Can the Assignee share some information about the status of this issue please?
I see that its listed as been blocked by two other issues but both seem to require some special permissions to see what are they about.
Is there any expected time frame for fixing this?
Why do some of the people report that the issue just went way for them without any action on their side?
I see that its listed as been blocked by two other issues but both seem to require some special permissions to see what are they about.
Is there any expected time frame for fixing this?
Why do some of the people report that the issue just went way for them without any action on their side?
go...@google.com
Hi !
This behaviour has been reported to be fixed. Are you still experiencing it?
Best regards,
so...@telenor.com
Hi there,
Just created a new project and the problem is NOT fixed. Still the same issues with permissions.
Error message:
Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In
wa...@gmail.com
i had one account that was affected, and corrected itself around 19th May
se...@gmail.com
has been for me since 19th may 2020.
ro...@gmail.com
My account seems to have recovered, too.
BUT note that the message says "temporarily disabled"
But even if the problem does correct itself after a while, a system that can suddenly lock you out for no obvious reason is seriously flawed.
BUT note that the message says "temporarily disabled"
But even if the problem does correct itself after a while, a system that can suddenly lock you out for no obvious reason is seriously flawed.
fi...@gmail.com
Same problem:
- Created new sheet
- Started new script
- Called GmailApp.getUserLabelByName(labelName);
- Ran script
- Attempted auth with same account that I just created script with
- Error. See attached.
- Created new sheet
- Started new script
- Called GmailApp.getUserLabelByName(labelName);
- Ran script
- Attempted auth with same account that I just created script with
- Error. See attached.
ma...@gmail.com
ma...@eset.com
This issue hasn't been fixed for me.
va...@google.com
se...@gmail.com
The problem went away on 19th May, but has returned for me today, I can no longer authorise Apps Scripts which utilise external requests again.
mr...@gmail.com
Different users are getting different errors.
I get:
Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In.
There is no recourse. Nothing to click on.
Another developer gets:
This App isn't verified.
This app hasn't been verified by Google yet. Only proceed if you know and trust the developer.
In his case, he has the Advanced option to click on "Go to Email Campaign." And when he does that, the script continues.
A third user has no issue.
The script actually runs: it places menu items into the Google Sheet. But upon trying to run the menu item, I just get completely stuck. I've had this issue for months.
I get:
Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In.
There is no recourse. Nothing to click on.
Another developer gets:
This App isn't verified.
This app hasn't been verified by Google yet. Only proceed if you know and trust the developer.
In his case, he has the Advanced option to click on "Go to Email Campaign." And when he does that, the script continues.
A third user has no issue.
The script actually runs: it places menu items into the Google Sheet. But upon trying to run the menu item, I just get completely stuck. I've had this issue for months.
ep...@gmail.com
Yes,
on one of my scripts I was somehow able to resolve this.
but when I just tried to create a Gmail addon I was able to deploy it using
the manifest but when it runs it says that authorization is required and
then when I want to authorize it It says that the App has not been verified
and thats it... nowhere to go from there and nothing to do.
I thought I might need to add it to the OAuth consent screen (
https://console.cloud.google.com/apis/credentials/consent ) page but the
addon script does not show as one of my projects
On Fri, Aug 7, 2020 at 10:10 AM <buganizer-system@google.com> wrote:
on one of my scripts I was somehow able to resolve this.
but when I just tried to create a Gmail addon I was able to deploy it using
the manifest but when it runs it says that authorization is required and
then when I want to authorize it It says that the App has not been verified
and thats it... nowhere to go from there and nothing to do.
I thought I might need to add it to the OAuth consent screen (
addon script does not show as one of my projects
On Fri, Aug 7, 2020 at 10:10 AM <buganizer-system@google.com> wrote:
mr...@gmail.com
I'm not experienced with the Google Issue Tracker. but I've just done my research and found this explanation of the priorities: https://developers.google.com/issue-tracker/concepts/issues
(I haven't found good documentation on the Severity scale.) But I do see that P2 is an issue that needs to be addressed on a reasonable timescale. Please, we've been faced with this completely script-busting bug for the better part of a year!
I've had positive feelings about Google, but this project-busting bug definitely changes that. I ask that the Priority and Severity be increased, to at P1 or P0. (and for me the severity is extreme, as it just completely disabled my capacity to run Google Apps Script.)
What I really seek is simply an account that I can use to run scripts successfully. If I could log in on that account, and just make it work (if it actually works) I'd be pleased enough.
It looks like va...@google.com has taken on the assignment of resolving this issue. SA: is there a way of granting me an account where I can successfully run scripts, while you continue to work on this crazy issue for all accounts?
Thank you for considering this request.
(I haven't found good documentation on the Severity scale.) But I do see that P2 is an issue that needs to be addressed on a reasonable timescale. Please, we've been faced with this completely script-busting bug for the better part of a year!
I've had positive feelings about Google, but this project-busting bug definitely changes that. I ask that the Priority and Severity be increased, to at P1 or P0. (and for me the severity is extreme, as it just completely disabled my capacity to run Google Apps Script.)
What I really seek is simply an account that I can use to run scripts successfully. If I could log in on that account, and just make it work (if it actually works) I'd be pleased enough.
It looks like va...@google.com has taken on the assignment of resolving this issue. SA: is there a way of granting me an account where I can successfully run scripts, while you continue to work on this crazy issue for all accounts?
Thank you for considering this request.
se...@gmail.com
Very strange, after loosing authorisation access about a week ago to a free account, I also lost authorisation access over the weekend to my g suite account. However today both are working again, so back to normal for now. Wish I knew whether this was something I was causing, so I could avoid it in future, or more importantly what I did to get it working again.
Happy to assist anyone from Google working on this if they want to reach out to me.
Happy to assist anyone from Google working on this if they want to reach out to me.
mu...@gmail.com
The issue is still there for me, and it's very frustrating. As a web agency that relies heavily on using scripts, this is really handicapping. Wish someone at Google could provide some much needed help
mr...@gmail.com
Adding a HAR file this time. I did not know if a HAR file would expose my actual data, so I've done this with a brand new sheet, but I'm getting the same error on a new empty sheet. "Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In." I hope this helps the troubleshooters at Google.
This app has not been verified yet by Google in order to use Google Sign In." I hope this helps the troubleshooters at Google.
mr...@gmail.com
This issue points to a MAJOR bug that has not been given the priority that it deserves.
It's been disabling google apps scripts for the better part of a year for people whose accounts are affected. I created a new account, but it's not easy to be switching back and forth from accounts (you can say it is, but in real life it's not), and worse yet, the new account can't edit the script made by my real account. It's not just a matter of starting anew, because a lot of people are using the file.
I hope that this issue gets the priority it deserves..
I'll add that asking people (November 2019, above) to post a HAR file without telling them that it shares sensitive information is quite problematic. Thank you for deleting the HAR file at my request. (I wonder if the request was public... thus pointing people directly to the sensitive information? I waited until the file was deleted to post that question.)
Please increase the priority given to this bug.
There are other issues, like the script won't send email unless I'm logged in as the owner of the script... etc. I need to be able to run scripts, and edit scripts. And I need to have my faith restored in Google again. This issue's bug is a real bugaboo.
I wondered if that was a real word, so I looked it up, and found that a bugaboo is a "a legendary scary creature." Having Google Apps scripts not work on any given number of accounts is that for me. It's just a mess. Okay, maybe not legendary, but is it actually common for a bug like this to go unfixed for so long? The bug is severe. App Scripts don't work.
It's been disabling google apps scripts for the better part of a year for people whose accounts are affected. I created a new account, but it's not easy to be switching back and forth from accounts (you can say it is, but in real life it's not), and worse yet, the new account can't edit the script made by my real account. It's not just a matter of starting anew, because a lot of people are using the file.
I hope that this issue gets the priority it deserves..
I'll add that asking people (November 2019, above) to post a HAR file without telling them that it shares sensitive information is quite problematic. Thank you for deleting the HAR file at my request. (I wonder if the request was public... thus pointing people directly to the sensitive information? I waited until the file was deleted to post that question.)
Please increase the priority given to this bug.
There are other issues, like the script won't send email unless I'm logged in as the owner of the script... etc. I need to be able to run scripts, and edit scripts. And I need to have my faith restored in Google again. This issue's bug is a real bugaboo.
I wondered if that was a real word, so I looked it up, and found that a bugaboo is a "a legendary scary creature." Having Google Apps scripts not work on any given number of accounts is that for me. It's just a mess. Okay, maybe not legendary, but is it actually common for a bug like this to go unfixed for so long? The bug is severe. App Scripts don't work.
va...@google.com
je...@gmail.com
Same here on a personal gmail account with a Google One subscription.
I began seeing this problem after enrolling in Google Advanced Protection program. It was a deal breaker to see my personal scripts not working, so I unenrolled from the program, but I still see the error.
I began seeing this problem after enrolling in Google Advanced Protection program. It was a deal breaker to see my personal scripts not working, so I unenrolled from the program, but I still see the error.
mr...@gmail.com
Google, is there a human being that I can talk to on the phone to share the impact of this bug?
Even on the new account I created, it's cropping up.
Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In.
This bug is not receiving the priority it deserves. And even at its current assigned priority, it's been out there for most of a year. so it's not meeting the standard of P2 priority...
Please, humans, let's resolve this.
Even on the new account I created, it's cropping up.
Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In.
This bug is not receiving the priority it deserves. And even at its current assigned priority, it's been out there for most of a year. so it's not meeting the standard of P2 priority...
Please, humans, let's resolve this.
su...@gmail.com
Error showing for one email address only, the same ID is added as an owner but no change. Other email IDs are working fine.
tg...@gmail.com
In my personal gmail account I created a new Google Sheet with a new Google Form and tried to add a trigger on a Form Submit and I am getting a Google Apps Script unauthorizable error. I don't understand why.
aj...@gmail.com
I am a former Googler and able to readily repro this issue. It occurs for me on a Gmail account with a brand new Google Form and Google Spreadsheet. It seems to recognize the spreadsheet as an "app" and since it's not on the allowlist (somewhere), it blocks you.
Don't know how we've gone 6 months without any resolution here.
This is a really bad bug with severe impact to those trying to author Apps Scripts.
Don't know how we've gone 6 months without any resolution here.
This is a really bad bug with severe impact to those trying to author Apps Scripts.
du...@gmail.com
Same problem here "Sign in with Google temporarily disabled for this app" when I try to run this test script from a Google tutorial:
function myFunction() {
function sendMap() {
var sheet = SpreadsheetApp.getActiveSheet();
var address = sheet.getRange('A1').getValue();
var map = Maps.newStaticMap().addMarker(address);
var url = map.getMapUrl()
sheet.getRange("B1").setValue(url)
}
}
Please fix it!
function myFunction() {
function sendMap() {
var sheet = SpreadsheetApp.getActiveSheet();
var address = sheet.getRange('A1').getValue();
var map = Maps.newStaticMap().addMarker(address);
var url = map.getMapUrl()
sheet.getRange("B1").setValue(url)
}
}
Please fix it!
gi...@gmail.com
I have been using Google Apps Script for 10 years and have written hundreds of scripts, notably running a webstore that processes 10k+ orders per year.
My main account just started experiencing the issue tonight: this is an absolute disaster !!
This bug looks totally random (encountered with one of my customer account) but it is quite severe.
Is there a way to get some support before it is fixed?
My main account just started experiencing the issue tonight: this is an absolute disaster !!
This bug looks totally random (encountered with one of my customer account) but it is quite severe.
Is there a way to get some support before it is fixed?
mu...@gmail.com
So Google hasn't done anything about this but if you still need your scripts to run, what worked for me are one of the following 3 workarounds:
1) Create a new project on Google Cloud Platform and assign it to my GAS script. This replaces the default GCP project that GAS creates for every new script, and seems to fix the issue.
Don't forget to go through the OAuth2 screen for your new project in GCP (left menu -> API and services -> OAuth consent screen). GAS will remind you if you don't anyway. Once that's done, I'm able to get the usual authorization screen again for this given GAS project. So what you can do is just run everything from that project I guess, by passing your other scripts as librairies or something.
2) This doesn't work for all API's, but will work for some, like SpreadsheetApp and some others. This only works for internal scripts too (can't be published). Add this at the top of your script and run it again:
/**
* @OnlyCurrentDoc
*/
3) If none of the above worked, and you really need to run a given script, you can still try running it through the Google Ads Scripts environment (if you have a Google Ads account). This might require some tweaking in the code, but the authorization flow works fine in Google Ads at least lol
1) Create a new project on Google Cloud Platform and assign it to my GAS script. This replaces the default GCP project that GAS creates for every new script, and seems to fix the issue.
Don't forget to go through the OAuth2 screen for your new project in GCP (left menu -> API and services -> OAuth consent screen). GAS will remind you if you don't anyway. Once that's done, I'm able to get the usual authorization screen again for this given GAS project. So what you can do is just run everything from that project I guess, by passing your other scripts as librairies or something.
2) This doesn't work for all API's, but will work for some, like SpreadsheetApp and some others. This only works for internal scripts too (can't be published). Add this at the top of your script and run it again:
/**
* @OnlyCurrentDoc
*/
3) If none of the above worked, and you really need to run a given script, you can still try running it through the Google Ads Scripts environment (if you have a Google Ads account). This might require some tweaking in the code, but the authorization flow works fine in Google Ads at least lol
so...@telenor.com
I also see that this was unassigned some time ago (mid september) and that nobody from Google has followed up on this since. How is it possible for a trillion dollar company to leave this critical issue open for so long?
ba...@gmail.com
same problem here
se...@gmail.com
Yet again I am locked out from authorising my own apps scripts in sheets.
It seems to be happening every month or so. No detailed explanation of what caused it on how to rectify it.
It's very disruptive to use other Google accounts to run scripts on our business sheets
It really isn't the reliability I've experienced from Google in the past, nothing ever this disruptive and unresolvable has ever happened before, and is really making me question investing further in Apps Script development for our business.
Please can we have a fix, or at least some attention to the problem to perhaps identify a pattern of actions we should avoid to prevent triggering whatever bug is causing this to happen.
Thanks
It seems to be happening every month or so. No detailed explanation of what caused it on how to rectify it.
It's very disruptive to use other Google accounts to run scripts on our business sheets
It really isn't the reliability I've experienced from Google in the past, nothing ever this disruptive and unresolvable has ever happened before, and is really making me question investing further in Apps Script development for our business.
Please can we have a fix, or at least some attention to the problem to perhaps identify a pattern of actions we should avoid to prevent triggering whatever bug is causing this to happen.
Thanks
[Deleted User] <[Deleted User]>
This is a super frustrating problem rendering Apps Scripts completely unusable for my organization.
I would recommend raising the priority of the issue.
I would recommend raising the priority of the issue.
is...@gmail.com
I can confirm that
This account is not in a GSuite organisation and my problem was with personal scripts doing things in calendar, mail, etc. Just like
As
- Create a new project on Google Cloud Platform and assign it to my GAS script. This replaces the default GCP project that GAS creates for every new script, and seems to fix the issue. Don't forget to go through the OAuth2 screen for your new project in GCP (left menu -> API and services -> OAuth consent screen). GAS will remind you if you don't anyway. Once that's done, I'm able to get the usual authorization screen again for this given GAS project. So what you can do is just run everything from that project I guess, by passing your other scripts as librairies or something.
I can't guarantee the following will work for you or that it won't make your project explode
Here's what I did in detail:
- Go to
https://console.cloud.google.com/cloud-resource-manager and click + CREATE PROJECT - Set project name and click CREATE. Wait for it to be created.
- Click on the ☰ menu button upper left >> APIs & Services >> OAuth consent screen
- Make sure that your new project is selected upper left to the right of Google Cloud Platform
- I chose External (I'm not a Google Workspace (formerly G Suite) user thus Internal was not an option for me or I would have used that) and click CREATE
- Fill in App name, User support email and Email address under Developer contact information and click SAVE AND CONTINUE
- On the Scopes section just click SAVE AND CONTINUE and on the Option Info section click SAVE AND CONTINUE
- Click on the ☰ menu button upper left >> Home >> Dashboard and copy the Project number under Project info to your clipboard
- Go to your google script code editor and click on the Resources menu >> Cloud Platform project.... My project was the one created by google for the script and said This script has an Apps Script–managed Cloud Platform project.
- Paste the Project number in the Enter Project Number here box and click Set Project
After that I ran a function from my script, went through the authorization process and I got the This app isn't verified warning. There was an Advanced button there which reveals a Go to <App name> (unsafe) link which allowed me to complete the authorization.
I hope this helps someone.
ac...@gmail.com
It does!
lo...@gmail.com
Update- This issue appears to be resolved for my account. I am now able to authorize scripts again. It started 'randomly' and resolved 'randomly' as well. Hopefully it stays that way and thanks to the engineers that fixed it.
se...@gmail.com
Still not working for me, like you say its random for each account it seems, there is no pattern to the duration or timing that I can tell. This is the third time it has failed for me this year, it will correct itself eventually.
ac...@gmail.com
Not working for me either.
Some scripts I was able to authorize via the normal path ("not safe" message >> click advanced >> go to [script's name]). Some I can not see that path (no "advanced" option on the authorization page).
I can confirm that #150 worked for me.
Some scripts I was able to authorize via the normal path ("not safe" message >> click advanced >> go to [script's name]). Some I can not see that path (no "advanced" option on the authorization page).
I can confirm that #150 worked for me.
me...@gmail.com
#150 worked for me
pi...@gmail.com
#150 worked for me too!
im...@gmail.com
Thanks - #150 worked for me
fi...@gmail.com
#150 worked for me too!
se...@gmail.com
Thanks very much for #150 & #145, I gave it a go and went through the process, which successfully allowed authorisation on two separate sheets/apps scripts, but now when I try to run script I get:
"Exception: We're sorry, a server error occurred. Please wait a bit and try again."
I tried yesterday and today and still the same error.
If I run the same scripts using another gmail account that is not normally prone to apps script issues, they both expereience the same error, presumably because they are also now associated with the new google cloud project.
I'm wondering whether #150 requires a separate project for each script, maybe that's the reason I'm having issues, or maybe as warned in #145 section 2, I'm using certain API that require review, which I think I read can take 3-5 days??? but in that case it doesn't explain the error I'm getting relating to server error???
Anyway I copied 2 new sheets and deleted the old sheets that had errors and started again using the default resource, so I could get them working again with the alternative google account.
For the time being using an alternative google account remains the best solution for me.
"Exception: We're sorry, a server error occurred. Please wait a bit and try again."
I tried yesterday and today and still the same error.
If I run the same scripts using another gmail account that is not normally prone to apps script issues, they both expereience the same error, presumably because they are also now associated with the new google cloud project.
I'm wondering whether #150 requires a separate project for each script, maybe that's the reason I'm having issues, or maybe as warned in #145 section 2, I'm using certain API that require review, which I think I read can take 3-5 days??? but in that case it doesn't explain the error I'm getting relating to server error???
Anyway I copied 2 new sheets and deleted the old sheets that had errors and started again using the default resource, so I could get them working again with the alternative google account.
For the time being using an alternative google account remains the best solution for me.
se...@gmail.com
okay so maybe there is a cap, which explains what I'm seeing, unless the sheet owner and user are within the same Google Workspace domain, you are going to eventually get the unverified app screen without the authorisation flow, if requesting certain sensitive OAuth scopes:
https://support.google.com/cloud/answer/7454865#unverified-app-user-cap
https://developers.google.com/apps-script/guides/client-verification
ma...@eset.com
When will we finally get a fix? I've just discovered that switching to a standard project stopped working for me :/ - the project number is not recognized at all!
go...@google.com
an...@gmail.com
Ah ha.. Progress.. It's been assigned to someone :)
go...@google.com
Hi !
Thank you all for your patience. If you experience problems regarding less secure apps, this might be due to a series of different reasons where Google has taken a series of signals to determine the risk level of the app. In order to make your app more secure please follow
If despite this guideline and the workarounds provided
Best regards,
kp...@gmail.com
I don't know whos decided to close this issue, but they really have no idea of what issue is about or what Google Apps Script is. What a shame.
Developers all over the world cannot run their scripts (from their profiles) and Google says it's intended behavior.
da...@icrossing.co.uk
Not being able to run an extremely simple script without an obviously clunky workaround that requires fiddling about in the GCP and only happens in random accounts is "Intended Behaviour"? And it took you 16 months to get to the bottom of this 'intended behaviour'?
[Deleted User] <[Deleted User]>
I can only agree with what's said in #165.
The fact that the authorization issue only affects random users and that every scope is categorized as sensitive renders apps scripts useless.
I'm not even that upset about the scope issue. At the end of the day everything can be deemed sensitive. Even something as simple as "SpreadsheetApp.getActiveSheet();".
But it baffles me how an issue affecting random users can be "intended behaviour".
The fact that the authorization issue only affects random users and that every scope is categorized as sensitive renders apps scripts useless.
I'm not even that upset about the scope issue. At the end of the day everything can be deemed sensitive. Even something as simple as "SpreadsheetApp.getActiveSheet();".
But it baffles me how an issue affecting random users can be "intended behaviour".
du...@gmail.com
After all this time and with such an unsatisfactory reply, what about spending some bucks and filing a class action against Google?
From: buganizer-system@google.com <buganizer-system@google.com>
Date: Monday, 1 March 2021 at 16:33
To: b-system+-1767823102@google.com <b-system+-1767823102@google.com>
Cc: duemme@gmail.com <duemme@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
https://issuetracker.google.com/issues/145162820
Changed
mi...@iihnordic.com addedhttps://issuetracker.google.com/issues/145162820#comment166 >:
I can only agree with what's said in #165.
The fact that the authorization issue only affects random users and that every scope is categorized as sensitive renders apps scripts useless.
I'm not even that upset about the scope issue. At the end of the day everything can be deemed sensitive. Even something as simple as "SpreadsheetApp.getActiveSheet();".
But it baffles me how an issue affecting random users can be "intended behaviour".
_______________________________
Reference Info: 145162820 Google Apps Script unauthorizable
component: Public Trackers > Google Workspace Developers > Apps Script<https://issuetracker.google.com/components/191640 >
status: Intended Behavior
reporter: se...@gmail.com
assignee: go...@google.com
cc: se...@gmail.com
type: Bug
priority: P2
severity: S2
blocked by: 145647425<https://issuetracker.google.com/issues/145647425 >, 149590111<https://issuetracker.google.com/issues/149590111 >
blocking: 160916894<https://issuetracker.google.com/issues/160916894 >, 160916897<https://issuetracker.google.com/issues/160916897 >
duplicate issue: 145623704<https://issuetracker.google.com/issues/145623704 >, 147835012<https://issuetracker.google.com/issues/147835012 >, 149815304<https://issuetracker.google.com/issues/149815304 >, 155847458<https://issuetracker.google.com/issues/155847458 >, 157480303<https://issuetracker.google.com/issues/157480303 >, 159455927<https://issuetracker.google.com/issues/159455927 >, 160056832<https://issuetracker.google.com/issues/160056832 >, 165942690<https://issuetracker.google.com/issues/165942690 >, 175291075<https://issuetracker.google.com/issues/175291075 >
retention: Component default
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTrackerhttps://issuetracker.google.com/issues/145162820 > where you have the role: starred.
Unsubscribe from this issue.<https://issuetracker.google.com/issues/145162820?unsubscribe=true >
From: buganizer-system@google.com <buganizer-system@google.com>
Date: Monday, 1 March 2021 at 16:33
To: b-system+-1767823102@google.com <b-system+-1767823102@google.com>
Cc: duemme@gmail.com <duemme@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
mi...@iihnordic.com added
I can only agree with what's said in #165.
The fact that the authorization issue only affects random users and that every scope is categorized as sensitive renders apps scripts useless.
I'm not even that upset about the scope issue. At the end of the day everything can be deemed sensitive. Even something as simple as "SpreadsheetApp.getActiveSheet();".
But it baffles me how an issue affecting random users can be "intended behaviour".
_______________________________
Reference Info: 145162820 Google Apps Script unauthorizable
component: Public Trackers > Google Workspace Developers > Apps Script<
status: Intended Behavior
reporter: se...@gmail.com
assignee: go...@google.com
cc: se...@gmail.com
type: Bug
priority: P2
severity: S2
blocked by: 145647425<
blocking: 160916894<
duplicate issue: 145623704<
retention: Component default
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
ac...@gmail.com
That is a shame, because Apps Script is pretty much useless for us as it is.
I can't write any new scripts, and the hoops I need to jump through in order to get something simple working takes the wind out of my sails. I don't even want to get to it, since I know I'll be disappointed with a simple call to integrate data from two of my sheets and generate what I need from there - something I can do with MS-Excel at any time and with no hassle wse.
Google, you might have security as a priority, but you've ruined the ability to use your platform for people the world over.
Just give us an "I trust my own apps to access my own data. Allow me to authorize them on the go." option.
I can't write any new scripts, and the hoops I need to jump through in order to get something simple working takes the wind out of my sails. I don't even want to get to it, since I know I'll be disappointed with a simple call to integrate data from two of my sheets and generate what I need from there - something I can do with MS-Excel at any time and with no hassle wse.
Google, you might have security as a priority, but you've ruined the ability to use your platform for people the world over.
Just give us an "I trust my own apps to access my own data. Allow me to authorize them on the go." option.
an...@gmail.com
Hi everyone,
I figured out a workaround!
For almost two years, I also struggled with this exact same issue, and felt the same level of frustration expressed by you all.
I really, *really* wanted to figure this out and begin writing Apps Script. I even sent a couple similar nasty-grams to Google.
Then, with help from you all in many different posts, I finally figured out the solution.
Today, I can write and run any Apps Script I want, avoiding all of those pesky errors!
I would also like to help you establish this same solution.
Given the sensitive nature of this situation in regards to information security, please contact me off list and I will help you.
PS: can someone please share with me the mechanics of how someone can contact me "off list" in this forum? Thanks very much.
I figured out a workaround!
For almost two years, I also struggled with this exact same issue, and felt the same level of frustration expressed by you all.
I really, *really* wanted to figure this out and begin writing Apps Script. I even sent a couple similar nasty-grams to Google.
Then, with help from you all in many different posts, I finally figured out the solution.
Today, I can write and run any Apps Script I want, avoiding all of those pesky errors!
I would also like to help you establish this same solution.
Given the sensitive nature of this situation in regards to information security, please contact me off list and I will help you.
PS: can someone please share with me the mechanics of how someone can contact me "off list" in this forum? Thanks very much.
hu...@gmail.com
Not sure what happened, but after a year, I'm now able to go to an advanced option to allow the app to access my files. Seems to work again.
mr...@gmail.com
What??? This was marked as intended behavior/ What in the curses?????
an...@gmail.com
bi...@gmail.com
I've found a workaround that takes advantage of the fact that while google seems to be blocking code from running when the user requests it (for their protection), it still happily will run code from the same App Script silently and automatically any time a sheet is loaded or edited, and this code is free to access and change any data in the sheet or document it pleases.
Here is a description of the issue and the workaround on Stack Exchange...
If anyone from the Google Cloud team ever reads this, well you should be embarrassed. It is one thing to say "Ok, this is very complicated and we broke something and we aren't really sure how to fix it so this might take a while be we are on it." We get that. But to say, "Um, yea, your account was randomly selected to participate in an undocumented system enhancement that blocks you from running your own scripts on your own documents in your own account in order to protect your sensitive data and keep you safe (but those very same scripts are free to run without any permissions pop-up at all and access and modify anything they want as long as they run automatically and silently in the background)" is incoherent.
AWS is not perfect, but I've never seen anything like this (and I've seen stuff like this at least three times on GCS).
an...@gmail.com
Hi @bi...@gmail.com thank you very much for the helpful information and the link to that other post. Also please see my previous comment for a solution: https://issuetracker.google.com/issues/145162820#comment169 hope to hear from you soon.
ti...@gmail.com
I followed #150, but had to:
* revert to the legacy code editor in order to see the "resources" for my script and reassign the project number.
* in the OAuth setup, I had to assign myself as a Test User.
Finally, I was able to get a security authorization dialog that allowed me to proceed and approve my own script to run on my own spreadsheet.
What a mess Google. The arrogance of closing this issue saying it's intended behaviour. Only when you debug why users are suddenly and randomly finding their scripts unable to run, and publish a workaround or fix the bug in Google Cloud, will this issue be resolved.
* revert to the legacy code editor in order to see the "resources" for my script and reassign the project number.
* in the OAuth setup, I had to assign myself as a Test User.
Finally, I was able to get a security authorization dialog that allowed me to proceed and approve my own script to run on my own spreadsheet.
What a mess Google. The arrogance of closing this issue saying it's intended behaviour. Only when you debug why users are suddenly and randomly finding their scripts unable to run, and publish a workaround or fix the bug in Google Cloud, will this issue be resolved.
gc...@gmail.com
Has this issue been resolved yet?
so...@telenor.no
Not solved to my knowledge.
Not sure how on earth this is supposed to be "Intended Behavior" which it is marked as.
Not sure how on earth this is supposed to be "Intended Behavior" which it is marked as.
da...@gmail.com
Do you have Google's advanced security enabled for the account where you have an issue?
ph...@gmail.com
Comment has been deleted.
ph...@gmail.com
This is ridiculous!
I just want to run A SIMPLE SCRIPT for my sheet and be blocked out.
Should I say thank you for google's strict safety regulations, or
should I blame myself for not paying enough efforts to solve this issue in last 3 days?
I just want to run A SIMPLE SCRIPT for my sheet and be blocked out.
Should I say thank you for google's strict safety regulations, or
should I blame myself for not paying enough efforts to solve this issue in last 3 days?
mr...@gmail.com
Appalling.
jo...@gmail.com
Post 76 was a workaround for me that was successful, but can confirm this is still an issue as of April 2022.
mi...@gmail.com
This issue has occured again. Please help
mi...@gmail.com
Won't Fix (Intended behavior)
Why this is intended behaviour? This is a bug! Is bug a intended behaviour?
Why this is intended behaviour? This is a bug! Is bug a intended behaviour?
to...@gmail.com
Adding myself to the list of affected users. I built a Google Sheet template with a couple of simple email reminders that the user can install triggers for with a button. 2/10 current users have to use workarounds because they can't even authorize the script. Not sure what I can do for them as they all work on separate copies of my sheet.
Description
It uses the UrlFetchApp.fetch() method and requires the
When I try to run the function through the editor, a popup appears "Authorization Required".
I press the "Review Permissions" button and go through the typical consent screen, submitting the exact same credentials used to create the script.
I get this back:
"Sign in with Google temporarily disabled for this app
This app has not yet been verified by Google in order to use Google Sign in."
Why? I thought this should be possible if you are the owner of the script...!?
Ironically if I supply credentials from a different account, I get the advanced option to go to the app anyway, not that it allows me to run the script...