[YouTube-API] Re: Urgent - well known app with 200,000+ users suddenly can't upload via oAuth2

We've had hundreds of error reports and lots of angry and frustrated users, and the reputation of our software has taken a major hit from this surprise change. 

We worked overnight for the last 12 hours to try to find a solution to this problem.

It apparently began somewhere between 2:00 PM and 5:00 PM PST yesterday, 4/24/2012.

We've tried to find any notice or warning about the change in the API documentation, but have so far not been able to find any.

So far, it seems that YouTube has, without warning, started returning a 62 character OAuth2 authorization code, instead of the previous 30 character OAuth2 code. 

Since there is no clear "best practices" way on how to universally parse out the authorization code -- and asking users to copy paste it themselves is absurd, we have instead always parsed it by finding a 30 character string in the browser title.

tokens = dlg.HTMLPageTitle.Split(new[] {' ', '='});

foreach (string ss in tokens)

                        {

                            if (ss.Length == 30)

                            {

                                AuthorizationCode = ss;

                                break;

                            }

                        }

Our temporary fix and replacement is this:

 if (tokens.Length > 2)

                        {

                            AuthorizationCode = tokens[2];

                        }

HOWEVER, we need a permanent best practices solution where we are not going to have our entire application become useless the minute YouTube changes the way they handle oAuth2.

On Monday, April 23, 2012 11:07:43 PM UTC-7, Dan S wrote:

Hello,

Recently (perhaps in the last 0-5 hours) my .NET based application which has an "upload to youtube" feature has started failing for all users during the oAuth2 authentication sequence.

Up until a few hours ago, the application worked fine for about 5 months straight.

I have double checked my YouTube Developer Key, Oauth2 Client ID, Client Secret, and Redirect URI .. everything is fine.

I have tried upgrading my app to use the latest versions of the following dlls:

DotNetOpenAuth.dll

Google.Apis.Authentication.OAuth2.dll

Google.Apis.dll

Google.GData.Client.dll

Google.GData.Extensions.dll

Google.GData.YouTube.dll

log4net.dll

Newtonsoft.Json.Net35.dll

Regardless, I still get:

Message: The remote server returned an error: (400) Bad Request.

StackTrace:    at System.Net.HttpWebRequest.GetResponse()

==========

I tried using the latest Google sample oAuth2 app:

Tasks.SimpleOAuth2

which is part of the "samples" package available here:

http://code.google.com/p/google-api-dotnet-client/wiki/Downloads

I get the same exact result, error 400 Bad Request.

So at this point I need to verify if the YouTube OAuth2 API is down for everyone, or is it just me? (developer id available via private communication on request)

If it is down for everyone, when can we expect it back up?

If it is down for just our developer ID, what can we do to fix this?

Thank you!

--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To view this discussion on the web visit https://groups.google.com/d/msg/youtube-api-gdata/-/hKFB9xtSJQcJ.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.