Hi,
Are you using your own Google Cloud Console project?
If you do, while the app is set to Testing, refresh token will expire every week. Publish the app without necessarily verifying it and reauthorize the plugin to avoid 7 days timeout.
Thread Starter
ljmac
(@ljmac)
AFAIK I have to use my own Google Cloud Console Project in developer mode, right?
Also, what do you mean exactly by ” Publish the app without necessarily verifying it”?
Under OAuth consent screen, if you don’t have a Workspace account, you need to set/have:
- User type set to External
- Publishing Status set to In Production
- Verification Status set to Needs verification (by clicking on the PUBLISH APP button)
Afterwards, reauthorize the plugin and you’ll get rid of the 7 days refresh token expiration.
Thread Starter
ljmac
(@ljmac)
In your documentation it says “You don’t need to verify it further since only a handful of users will access it.” But when I publish the app it says it needs verification – is this actually necessary, or did I get something wrong in the setup process? In order to do verify it, I have to submit a YouTube video with the following info:
Your YouTube video should demonstrate the OAuth grant process by users and explain, in detail, how you’ll use sensitive and restricted scopes within the app’s functionality for each OAuth client belonging to the project. Learn more
The video should clearly show the app’s details such as the app name, OAuth client ID, and so on.
Thread Starter
ljmac
(@ljmac)
Ah, I found I could authorise the plugin if I clicked on Advanced when Google showed me a warning screen, then agreed to “accept the risks”. It might be a good idea to add this to the instructions – I was stuck in testing mode because I thought I had to verify.
