Hello, I have confirmed that this is because the OAuth token generation no longer supports IE6. The WebControl identifies itself as IE6, and therefore is disallowed by the server side.
The .NET client library team is currently working on an update to the token generator tool for the library. The updated code, once it is released, can also serve as an example for how to update your own code. Please keep an eye on the .NET github client library page for updates: https://github.com/googleads/googleads-dotnet-lib Regards, Mike, AdWords API Team On Friday, August 5, 2016 at 7:25:18 PM UTC-4, San Mehat wrote: > > A little bit of digging (via my favorite search engine) yielded the > following > <http://stackoverflow.com/questions/17922308/use-latest-version-of-ie-in-webbrowser-control> > article > which provided a solution for me that works. > > Specifically the following snippet from 'RoolWillie > <http://stackoverflow.com/users/1715044/rooiwillie>': > > int BrowserVer, RegVal; > > // get the installed IE version > using (WebBrowser Wb = new WebBrowser()) > BrowserVer = Wb.Version.Major; > > // set the appropriate IE version > if (BrowserVer >= 11) > RegVal = 11001; > else if (BrowserVer == 10) > RegVal = 10001; > else if (BrowserVer == 9) > RegVal = 9999; > else if (BrowserVer == 8) > RegVal = 8888; > else > RegVal = 7000; > > // set the actual key > RegistryKey Key = > Registry.CurrentUser.OpenSubKey(@"SOFTWARE\Microsoft\Internet > Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION", true); > Key.SetValue(System.Diagnostics.Process.GetCurrentProcess().ProcessName + > ".exe", RegVal, RegistryValueKind.DWord); > Key.Close(); > > > > Hope this helps :) > > -San > > On Friday, August 5, 2016 at 11:46:23 AM UTC-7, Michael Cloonan (AdWords > API Team) wrote: >> >> Hello, >> >> I apologize for the slow response time. I have escalated the issue within >> engineering and hopefully will have more information to share soon. >> >> In the meanwhile, the .NET client library team for the AdWords and DFP >> APIs have been made aware of this change and are looking into if there are >> any workarounds. >> >> I will post again here as soon as I know more. >> >> Regards, >> Mike, AdWords API Team >> >> On Friday, August 5, 2016 at 2:32:51 PM UTC-4, San Mehat wrote: >>> >>> I'm running into the same issue - to my untrained eye it looks like the >>> Browser control that .NET uses to back Windows.Forms.WebBrowser is no >>> longer supported by whatever server component handles Auth... :\. Changing >>> your default browser will have no effect. >>> >>> Best, >>> -san. >>> >>> >>> On Thursday, August 4, 2016 at 10:15:35 PM UTC-7, gajender singh wrote: >>>> >>>> Hi Mike, >>>> We have the exact same issue. Any help would be appreciated. >>>> >>>> On Thursday, 4 August 2016 17:51:36 UTC+5:30, Michael Cloonan (AdWords >>>> API Team) wrote: >>>>> >>>>> Hello, >>>>> >>>>> I apologize for the inconvenience. I have alerted our engineering team >>>>> and will update this thread with information as I get it. >>>>> >>>>> Regards, >>>>> Mike, AdWords API Team >>>>> >>>>> On Wednesday, August 3, 2016 at 4:18:37 PM UTC-4, [email protected] >>>>> wrote: >>>>>> >>>>>> I've been following the instructions on >>>>>> https://developers.google.com/adwords/api/docs/guides/first-api-call >>>>>> and have gotten to the section titled "Get an OAuth2 refresh token and >>>>>> configure your client". The instructions on >>>>>> https://github.com/googleads/googleads-dotnet-lib/wiki/API-access-using-own-credentials-(installed-application-flow)#step-2---setting-up-the-client-library >>>>>> say >>>>>> to use OAuthTokenGenerator.exe to generate the token. When I run the >>>>>> tool >>>>>> and the web form opens, it redirects to a page that says "Your browser >>>>>> is >>>>>> not supported anymore. Please update to a more recent one". I've tried >>>>>> this >>>>>> on several computers (Win 8.1, Win 7). I've also tried making Chrome the >>>>>> default browser but it still seems to open the web view in an IE control. >>>>>> >>>>>> Not sure where to go from here. Any assistance is appreciated. Thanks! >>>>>> >>>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] 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 Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/be746d5e-66bd-421a-8778-fd3508483ab8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
