I have got a Google project with authoriaztion code flow. A frontend redirects a user to the Google’s URL(https://accounts.google.com/o/oauth2/v2/auth) for authentication and getting codeToken, which later will be sent to a backend server (the last one gets accessToken and refreshToken using a passed codeToken)
When a user’s browser’s profile has got ONLY one google account – frontend app redirects to Google’s auth URL with prompt=none. If a user has already authenticated in my app and give all permissions – a consent screen doesn’t apear again. But when a user’s browser’s profle has got MORE THAN ONE google accoount – frontend app redirects to Google’s auth URL with prompt=select_account. If a user has already authenticated in my app a consent screen appears, a user select account and after it a user again gives permission to the app. I spent 4 days to solve it, but can’t force Google only to asks which account to use without asking again permission. Maybe, it’s correct behavior, but I didn’t find it in docs.

You have indicated that your app has features related to “email reporting and monitoring”, as defined in the Gmail user data and developer policy. This is specified in the Google Cloud Platform Console under the Scopes section of the OAuth consent screen page. We would like to remind you that starting June 3, 2024, apps that use information from emails to provide reporting or monitoring services will require periodic Gmail access renewals. This change helps protect privacy and security for new and existing users.
What do you need to know?

I got the following in an email from Google:

I got an email from Google saying:

I am using google sign in service (https://developers.google.com/identity/gsi/web/guides/personalized-button) with renderButton API. It seems to me that the button does not listen to the options you send.
enter image description here

I received this email and would like to inquire with the Google OAuth Team about a matter. In our app, after the user starts the app, they are prompted to log in. If they choose to log in with Google, the permissions are limited to login-related scopes only. Within the app, there is integration with Google Fit. Currently, the logic in the code is to first perform the Google login (with scopes limited to login-related), and then, upon successful login, request Fit scope permissions, similar to incremental authorization. Would this implementation be affected by the adjustment to granular consent controls? Since I am unsure how to verify this, I am seeking confirmation from the Google OAuth Team that this logic will not be impacted. Thank you.（Android）

For an application using google-oauth, I filled in the email reporting and monitoring permissions and was notified that I need to renew my subscription before I can access it. If I delete this access, do I no longer need to renew my subscription? My application does not use email. reporting and monitoring, the scenario I use is