I just provided the client ID via private email. It's worth mentioning that this is probably not a bug--no error code, as I believe things are functioning as they were designed to. But the design does not seem to take my edge-case into consideration. What do users do in the event that they want to create an "internal app" but have already established a lot of dependencies using a setup built with @gmail emails? It would seem the only option might be to restart our presence on the Google platform using internal emails...though this would be incredibly difficult.
On Thursday, November 17, 2022 at 9:11:14 AM UTC-8 Chad Wood wrote: > Screenshot located at the bottom of this message. > > A breakdown: > We can not create an "Internal" app because we are not Google Workspace > users > -> We can not become Google Workspace users because we are using @gmail > emails > ---> We can not convert to using internal emails because we are already > deeply intertwined with the current setup as a tech company > > So by what I understand, our only option is to use "External" for our app. > But that does not change the fact that this app is internal--for > reporting. Therefore, we can not "Publish" the app. > Since the "External" app is "Unpublished", our refresh tokens expire every > 7 days automatically. > > I will privately email client id > > > [image: g3.png] > > On Tuesday, November 15, 2022 at 11:02:10 AM UTC-8 adsapi wrote: > >> Hello, >> >> The team is going to need some more information to completely debug. >> Since this support avenue is not available for external clients, I will >> have to serve in the middleman in this exchange. Keep in mind that I don't >> actually have much expertise in the OAuth console, so I will generally be >> providing your responses as is to the team that is helping me. >> >> Here is the information they've provided me so far and the information >> they'll need from you: >> Due to admin restrictions, Workspace users can be blocked from granting >> access to a test app. However, a gmail.com project owner should not be >> blocked from changing their app's publishing status due to Workspace >> specifically. I will definitely need more details to nail down what the >> issue is. If you could please ask the customer to provide clarification on >> what "denied access" means in relation to Google Workspace, that would be >> helpful. Additionally, are they trying to change their app's publishing >> status from the OAuth consent screen page in the cloud console? >> Screenshots, a copy of the error message(s), and the client ID would be >> very useful for debugging. >> >> Can you provide the requested information so I can pass it along and >> hopefully find some kind of resolution? >> >> >> Regards, >> Mike, Google Ads API Team >> >> >> ref:_00D1U1174p._5004Q2ewsYl:ref >> > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 "Google Ads API and AdWords 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/92950c3b-0cab-4ecc-90ee-99f041bd051an%40googlegroups.com.
