Error while generating refresh token - in Production mode

[Vamshi Merugu]

Hi Team ,

We are planning to send conversion data to post to google by using enhanced conversions.

For this purpose, for authentication, we are using Oath2 flow for desktop/ web application to generate refresh token using python client libraries & We want to use the same refresh token for our daily process to call google client libraries.  

• As our app status un testing mode, the refresh token is expiring after 1 week. T fix the refresh token expiration issue after 1 week, google team has earlier suggested to publish the app instead of working in testing mode.
  • But, after publishing the ap, refresh token generation is not working. (please find the attached screenshot for the issue) 
• If we switch back to testing mode again, we can successfully generate the refresh token. 
  • We are having issue for production implementation. We dont want the refresh token to expire once we go-live. 
• Based on previous suggesions, we tried to see if we need to verify app. But, in GCP its clearly showing that "verification not required" 

Appreciate your help. 

Thanks,

Vamshi

[Google Ads API Forum Advisor]

Hi Vamshi,

Thank you for reaching out to the Google Ads API support team.

Please note that as per this guide, 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. As per seeing the screenshot you have provided, it appears that you have encountered an Unverified app warning. That said, I would suggest the below guides which are mainly about the verification process:

• How to verify: OAuth API verification FAQs - Google Cloud Platform Console Help
• General information: Unverified apps - Google Cloud Platform Console Help

Regards,

Carmela Google Ads API Team

ref:_00D1U1174p._5004Q2hMygW:ref