The application will disappear from the list of applications with the received access

[Алексей Чигинцев]

Hi, and first of all, I'm sorry for my lame English.

We were transferred from the Google Ads group with a question about access via the Oauth 2 protocol (the original post (the second problem): https://groups.google.com/u/1/g/adwords-api/c/da12F8dy_ZI ), however, I'm still not sure that I'm writing to the right group. Please correct me if I'm wrong.

I duplicate the problem from the original post:

2) From time to time, we have problems with updating the token, or rather, we simply can not use the refresh_token

This is what it looks like:

2.1) We allow the app access manually and get the first access_token and refresh_token. At this stage, everything is OK, the application is in the list that was granted access (check through this page: https://myaccount.google.com/permissions ): 

2.2) AcessToken successfully used and updated for some time (usually several weeks), but then the app from the list of apps that got access disappears:

https://myaccount.google.com/permissions

And disappears as if someone manually denies him access.

And, of course, the last access_token stops working, and with it the refresh_token.

After that, we again need to manually confirm the app's access for the first time. Because refresh_token, certainly, is not valid after the app disappears from the list.

Please tell me what this might be related to. And for what reason can an app disappear from the list ( https://myaccount.google.com/permissions Third-party apps with account access

 ) if no one manually restricts access to app?

Maybe there are some reasons: improper use of tokens and so on-the reasons why the application may disappear. Or private account settings that we don't know about? We will be glad to receive any suggestions, thank you in advance.

[Shawn Wu]

the issue seems specific impact on your service. To ensure the team have deeper investigation, please open a support case in the cloud console, in this way allowing us to assist you specifically.

[Алексей Чигинцев]

HI, thank you, but we have already solved a problem.

It turned out that we missed a small paragraph in OAuth2 documentation:

https://developers.google.com/identity/protocols/oauth2?hl=en

>> A Google Cloud Platform project with an OAuth consent screen configured for an external user type and a publishing status of "Testing" is issued a refresh token expiring in 7 days.

This is exactly what happened with our application. The token was reset after a week. 

The support recommended to transfer the application to production, we have already written off with the support of Trust and Safety. 

This topic can be closed, thank you very much for the answer.

воскресенье, 4 июля 2021 г. в 18:42:00 UTC+3, Shawn Wu: