OAuthTokenGenerator.exe reports "Your browser is not supported anymore. Please update to a more recent one"

[ry...@tldpros.com]

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!

[Michael Cloonan (AdWords API Team)]

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

[ad...@gmail.com]

We have the exact same issue. Any help would be appreciated.

[gajender singh]

Hi Mike,

We have the exact same issue. Any help would be appreciated. 

[San Mehat]

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.

[Michael Cloonan (AdWords API Team)]

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

[San Mehat]

A little bit of digging (via my favorite search engine) yielded the following article which provided a solution for me that works.

Specifically the following snippet from 'RoolWillie':

 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

[Michael Cloonan (AdWords API Team)]

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