Fix Google OAuth Error 403: access_denied in in 3 minutes #googleoauth #oauth
Why Stack Overflow recommends it
Stack Overflow users link it when a Google API app returns 403 access_denied because the project is still in testing and the account is not listed as a test user.
Recommended by 2 people across 3 different months, 2021 to 2022.
What it is
A short screen-recorded tutorial from Google Developer Expert Linda Lawton (DAIMTO) showing how to fix the Google OAuth "Error 403: access_denied" message. It walks through the OAuth consent screen in the Google Cloud console and explains how to add test users or publish the app.
What people said
Recommends Linda Lawton - DaImTo · 2021-03 · Stack Overflow · on “google oauth screen doesn't show up”
Go to google developer console under consent screen you will find [LINK] While your application has not been verified you can add additional users here these are your developers who will be able to access your application while it is still in development. I have a video which walks you through how to add the users. Google OAuth Error 403: access_denied easy fix. [this video]
Recommends Linda Lawton - DaImTo · 2022-01 · Stack Overflow · on “How can I get a user's calendar data from Google Calendar API?”
403: access_denied The developer hasn’t given you access to this app. Google OAuth Error 403: access_denied easy fix. [this video] This is a common error when your application is still in the testing phase. You need to grant your test users permission to access your application. In google developer console under your consent screen just click add users. [LINK] Note: you can only have 100 test users and you cant remove them once they have been added.
Recommends cegredev · 2022-06 · Stack Overflow · on “I can't set up **** clasp run ****”
Your project is still in testing; you either need to add the account you're trying to authorize as a test user, or set the project's publishing status to "In production" i.e. publish it. Here's a video that shows you how: [this video] The sidebar in that video isn't quite up to date however: I recommend searching for oauth in the top bar while having the appropriate project selected and clicking on OAuth consent screen . [LINK]
Cites OJNSim · 2021-10 · Stack Overflow · on “testing google sheet editor addon fails with error 403”
I have a Sheets editor addon. it is a stand alone project connected to a standard google cloud project (as opposed to the default project). I want to "Publish -> Test as add-on..." from the legacy editor menu. I choose one document owned by same account Set "installed and enabled" on the bottom of the same screen addon is now added to the document Addon menu When launching the addon, there's a prompt for Authorization approval. but at the end I get an Authorization error 403. see attached screen shoot. This youtube [this video] video suggest to add a user in the OAuth consent screen. so I did, but it didn't help. Please advise. [LINK]