I am trying to use Google Apps Script together with Google Sheets to get API data from a bank to my online table, but looks it is absolutely impossible. Every time I do it, I get these messages:
"Authorization required
Exchange Rate Table needs your permission to access your data on Google
Google sign-in is temporarily disabled for this application
This app has not yet been verified for Google Sign-in".
What kind of authorization Google needs again? I tried to learn at the Google Identity Platform, but found there 10 page instructions with a lot of useful hyperlinks. I need a university course at least to understand it.
This is a known issue regarding Apps Script.
I suggest you star the issue and eventually add a comment saying that you are affected by it.
Related
I have tried using this Google Ads Script along with a Google Sheets Template found in this article: https://searchengineland.com/script-automates-adding-adwords-data-google-spreadsheet-277724
Link to my Spreadsheet: https://docs.google.com/spreadsheets/d/1XyF8V4Xhi7MLNwDWGsHV3a10M-g9HiAD0sWGLh9wfak/edit?usp=sharing
Google Sheets: When I click;
AdWords Data Grabber from Optmyzr - Choose Report Type - Selecting any report
I have to approve the app. But then I get an error saying;
This app is blocked
This app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked this access.
Does anyone know how to get around this?
It also seems like the onOpen function fail
If the app doesn't meet Google's security standards, Google may block access to your account through them by default. Less secure apps can make it easier for hackers to access your account, so blocking sign-in from these apps helps keep your account secure.
You can try to bypass it via:
https://myaccount.google.com/lesssecureapps, but understand that you are putting yourself at risk.
Source
I made a fun spreadsheet to exercise basic math for my kids, but when they are logged on their kid account, they can not run any scripts (no fancy script, just copy-paste macro). After script authorization request they got error 403.
Chyba 403: access_denied
Podrobnosti požadavku
access_type=offline
login_hint=hanzalek.ben#gmail.com
o2v=1
hl=cs
response_type=none gsession
redirect_uri=https://script.google.com/oauthcallback
state=14621511234839642112
client_id=433541798399-h1ncj2ckkapf2gkcoo59mjv46kem0c88#developer.gserviceaccount.com
display=page
prompt=consent
scope=https://www.googleapis.com/auth/spreadsheets.cu
When I access the spreadsheet from another adult account everything runs.
link to the spreadsheet (you may copy it and use it for your kids if you wish :):
https://docs.google.com/spreadsheets/d/1Jy1hHgyCkkIJv26attxikKpJlYb_hjWXTauXMjVyn8E/edit?usp=sharing
Answer:
It appears that there is a restriction for Kid/Child accounts where Apps Script it not available. As long as your children have restricted accounts, there is nothing you can do about this.
More Information:
I did some testing and was able to reproduce the behaviour. These are the results of my tests:
If the account is a child account, the 403: access_denied error is received when trying to run a script from a Spreadsheet.
If the account is a child account, even if they create a new Sheet themself, they do not have access at all to the script editor. This heavily implies that child accounts do not have any Apps Script permissions/abilities at all.
If the account is not a child account, but the account is set up to be supervised in the family group at https://families.google.com/families, they can both run the script written by another account, and they have access the Script editor.
After searching the Family Link settings for the kid account, I was not able to find any setting which allows this to be turned on. I did some searching and I wasn't able to find any specific documentation either from searching on Google or on Google Help.
I did however find a couple of other Stack Overflow questions in which people have had the same error, and this was also the result of their findings, which I have included below.
Google Issue Tracker:
As there doesn't seem to be anywhere that publically mentions this specific Apps Script restriction, I suggest that you file a bug on Google's Issue Tracker for this, in the linked Apps Script component. They might be able to give you more insight into this behaviour.
In the mean time, it appears the only workaround for this is to have the users of the kids accounts use non-kids accounts while using these Spreadsheets, or maybe looking into embedding the Spreadsheet in a web app and have the scripts execute as you rather than the currently logged-in user. More infor about this can be read here
Relevant Questions:
New Google Account not able to access script.google.com
“Can't visit this page” error when trying to access Google Scripts
References:
Your family on Google
google "kids" apps script 403 - Google Search
Search results for kids apps script 403 - Google Help
Google Issue Tracker
Web Apps | Apps Script | Google Developers
there.
First time poster here. I've been using GAS to build a personal app that takes Telegram input and posts to a Google Sheet. It's a very simple app that helps manage a budget. I'm trying to extend the functionality to allow a couple friends who have expressed interest to post their own transactions to their own Google Sheets hosted on their own Google Accounts.
Right now the only way I can see to do that is to have them "share" their Google Sheet with my user account, which is obviously not preferable. I'd like the app to have authorized access, which would obviously require them to grant the access, but don't want a "shared" sheet.
Is there any way to do this within the Google App Script Editor enviroment? Or do I have to switch everything over to something like Google Cloud? If the latter, can anyone point me toward a tutorial on getting that done?
Thanks in advance.
I am considering using Google Spreadsheets and Google Apps Scripts for our business rules, given that Spreadsheets will make the business rules available and editable to non-technical employees.
My concern is about all the quotas that apply to Google Apps Scripts, as these also might change in the future, and there is no way to upgrade to a "premium" with more liberal quotas.
As a fall-back I am considering using the Google Spreadsheets API, and I assume that there are also quotas on this API, but I cannot find them anywhere. Does anyone know them? Or has anyone hit these quotas?
I am also trying to get some sort of idea of whether it is indeed a good idea to put the business rules in Google Spreadsheets in my question here.
There is an Apps Script Dashboard which identifies any service disruptions, as well as a tab for a breakdown of quotas, based on your Google Apps account type.
Google Apps Script Dashboard
From a quick skim of your posting on StackExchange, one thing to be mindful of is the email quota (1500 total recipients per account each day). You may be able to offset this hurdle (if applicable) using Google Groups, either by creating predefined groups, or programmatically building groups using Advanced Google service in Apps Script (at least for internal communications; direct add accounts for external addresses require a welcome message).
I'm not familiar with Ultradox, but using Apps Script, you can populate Google Doc "Template" files, convert them to PDF, and attach in Gmail (or provide the share link), right from Apps Script.
I have an app that consists of two parts
an installed application (more specifically: a browser add-on) that runs on the user's machine, and
a web app implemented as a stand-alone Google Apps Script app using HtmlService.
The two parts talk to each other and both access some Google APIs on behalf of the user via Oauth. To do this, I set up an API project in the Google API console. In the section "API Access", I created a client of type "Installed Application" for the browser add-on. For the Apps Script part, Google takes care of the authorization flow automatically.
My problem is that Google does not know that these two clients are part of the same project. Therefore, the user has to go through two authorization steps in a row when executing my app for the first time (first, the Oauth process for the browser add-on and then the automatically generated authorization process from Google Apps Script). This is very confusing to the user, especially, since the splitting between the browser add-on and the web app is rather an implementational detail about which the user shouldn't really have to bother.
Is there a way to unify the two authorization flows? I know that one can add several distinct clients to a single project in the Google API console. It seems to me like this feature is explicitly intended for scenarios similar to mine, where more than one application make up what is perceived as a single service by the user. Unfortunately, web apps that are implemented in Google Apps script don't seem to be compatible with the Google API console because of the way Apps Script generates the authorization flow automatically. Or am I missing an option in the API console or in the Apps Script editor?
For future reference: I found out that Google automatically creates an API project in the Google API console for each Google Apps Script project. This seems to be a fairly recent feature. One difficulty for me was that these API projects don't show up when one goes to the API console, clicks on the name of whatever project is currently opened in the upper left corner and chooses "open". Apparently, the only way to reach the auto-generated API project is as follows:
Go to drive.google.com and open the Google Apps Script project.
Chose "Resources --> Use Google APIs...".
In the popup, click the link to the Google API console.
In principle, this should allow to add additional clients to the project, as long as none of the other clients is also a Google Apps Script project. I haven't been able to test this since it still doesn't solve my specific problem: Sending e-mails from the user's Gmail account seems to be a feature unique to Google Apps Script and I couldn't find an Oauth2 scope for this operation. Therefore, I still cannot ask for all required permissions in a single authorization flow. But if anyone who's reading this has a similar problem with different Oauth2 scopes, the above instructions should fix it for you.
Anyway, I solved my problem in the meantime by no longer using Google Drive to upload files.