Hi Matt, Is there an issue # to track this? I'm definitely seeing intermittent refusals for tokens with a different amount of waiting time each time, at the request_token, access_token and protected resource stages. I was just curious if this was still a live issue.
On Feb 23, 2:31 pm, Matt Sanford <[email protected]> wrote: > Hi there, > > I am working on a fix for the case where a brand new token takes > a few seconds to propagate to all of our database slaves. During that > time you would see errors like "Invalid / expired Token" and then they > would suddenly start working. They may even work on some requests and > not others because you don't hit the same database every time. Like I > said, working on a fix for it now. Once the fix is done I'll keep and > eye out for more reports like this. > > Thanks; > — Matt > > On Feb 21, 2009, at 02:47 PM, Santosh Panda wrote: > > > Hi Paul, > > We see the same issue couple of times but infrequently. In another > > threaded mail, few more developers have conveyed the same. > > > cheers, > > Santosh Panda > >www.twitblogs.com > > > On Sat, Feb 21, 2009 at 9:50 PM, Paul Kinlan <[email protected]> > > wrote: > > Hi, > > > Following on from my previous email about not being able to use > > verify_credentials, I am still having sporadic problems and I am > > wondering if anyone else has seen them. > > > Our page call creates a request_token and navigates to the the > > twitter oAuth page, on successful return we swap our tokens for an > > access token, we then call verify_credentials.json. Sometimes > > (quite often) when we call this method we get a 401 Un-authorised > > exception. If no-one else see's this then I will have to see if the > > library I am using has the problem. > > > Kind Regards, > > Paul Kinlan.
