Google Synchronisation Problem

[Sandro Stross]

Hello,

I am having an issue with Google synchronization.

Every 7 days, I have to disable synchronization and re-authenticate with my Google Account, which inevitably leads to duplicate entries.

According to Google, this is normal because the Publishing Status in the Google Console for APIs and Services under the OAuth consent screen is set to Testing. Google states the following:

---

Publishing status The publishing status setting impacts the potential audience and potential authorizations of a project configured with a user type of External.

Testing Projects configured with a publishing status of Testing are limited to up to 100 test users listed in the OAuth consent screen. A test user consumes a project's test user quota once added to the project.

Google will display a warning message before allowing a specified test user to authorize scopes requested by your project's OAuth clients. The warning message confirms the user has test access to your project but should consider the risks associated with granting access to their data to an unverified app.

Authorizations by a test user will expire seven days from the time of consent. If your OAuth client requests an offline access type and receives a refresh token, that token will also expire.

A Brand Account may authorize scopes requested by your project's OAuth clients if a specified test user manages the Brand Account.

The only exception to this behavior is if your app requests a subset of the following: name, email address, and user profile (through the userinfo.email, userinfo.profile, openid scopes or their OpenID Connect equivalents). For such requests, your users do not need to be in the trusted user list, they will not see a warning message, and their authorizations will not expire after 7 days. If your app uses Sign in with Google to authenticate users, then this exception also applies. If your app requests any other OAuth scopes, then this exception does not apply.

A test user may be unable to authorize scopes requested by your project's OAuth clients due to the availability of Google Services for the account or configured restrictions. A Google Workspace may control which third-party apps access its data or an account enrolled in Advanced Protection may block most non-Google apps.

---

What can I do about this? This issue is not documented in any How-To guides for Easy Appointments, and it seems like I am the only one experiencing this.

Best regards.

[Alex Tselegidis]

Hello! 

You can change the state of the published services in the Google Cloud Console to production. 

Doing so the mode will change and you will not need to re-auth every week. 

Alex Tselegidis, Easy!Appointments Creator
Need a customization? Get a free quote!

[Sandro Stross]

Is there any guide on how to do this? Google requires verification, and simply switching from Testing to Production is not possible. They request a YouTube video of the service and how it works, as well as a link to the privacy policy, which is not possible because it is embedded.How should we proceed if there is no guide available? I believe a guide would be helpful since there is not much good information available online. Each web app is unique and requires different steps.

[Alex Tselegidis]

Hello! 

Normally you can switch to production even if your app is not verified. 

The verification step applies mostly to SaaS apps that have many users linking to their google accounts.