Hello, Thank you for offering a solution by creating a new GCP project, however the problems are:
1. All existing authenticated clients will require reauthentication which is a MAJOR problem. 2. Creating a new GCP project will require going through new OAuth consent screen verification which is very time and resource consuming both ours and google resources as well. This issue of "One developer token" attached per GCP project was never disclosed or mentioned in any place - neither documentation, nor policies. As it is critical and can't be changed for now, which creates a big problem, please add this to your documentation Is there a solution on the horizon for changing this token association or removing this requirement? What is the solution right now? Thanks -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/51f2595b-4993-4797-ad63-129e70b2457d%40googlegroups.com.
