Refreshing the access token. about oauth2client HOT 5 CLOSED

Ah, I just found a section of code commented out with the reason...

TODO: check for status code once the bug returning 500 is fixed

Could you possibly shed some light on this? Thanks

from oauth2client.

Can you tell me which services you are using OAuth? Some services (e.g. Yammer, Google) serve the refresh token in wired ways, so that it will not be parsed correctly.

I usually overload the access token parser via a category in that case. Here is an example that works for Yammer

from oauth2client.

The OAuth service is an in house one.

I've just found the problem.

In the section I mentioned above...

• (void)connection:(NSURLConnection *)connection didReceiveResponse:(NSURLResponse *)theResponse;

in

NXOAuth2Connection

The authenticationHeader was null as I wasn't getting back the 401 error reason (expired_token) from the server.

We are now writing that into the return error so hopefully this should be resolved.

If it doesn't fix it I'll let you know.

Thanks for the reply.

Oliver

from oauth2client.

@ojfoggin Also please let us know if it does fix it ;)

from oauth2client.

Hi again,

Yes, that worked perfectly.

Thanks

Although, I have found something else that didn't quite work but I'll add a new issue for this as it's not really related.

from oauth2client.