Hi Damon, We've heard some reports of iPads setting their dates/clocks incorrectly -- sometimes back to 1969. If the client application uses the date/time on the machine (rather than querying it from some other source), and the date/time isn't within 5 minutes or so of our clocks, it results in a failed request. One work around is for clients to adjust their concept of the "current time" by looking at the HTTP headers we send on a failed request (which includes our server clock), or to use an external service to fetch the time prior to making a request.
Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, May 20, 2010 at 2:04 PM, Damon Clinkscales <[email protected]> wrote: > Just tried establishing a new connection to a different account with > Twitterrific (which I believe uses xAuth) and it worked fine. > > So, there is presumably a bug in the iPad client I was testing. Unrelated. > > -damon > On Thu, May 20, 2010 at 3:33 PM, Damon Clinkscales <[email protected]> > wrote: > > Hey guys, > > > > Don't know if this is related, but I was testing a friend's iPad app > > this morning which uses xAuth. > > > > When setting up a new account in his app, the app authorizes in my > > Connections tab. However, whenever his app tries to use the tokens, > > we get an immediate HTTP 401. None of the calls with the tokens he > > has received are working for accessing. > > > > His account, which was auth'd (tokens retreived) over a month ago, > > still works ok with his app, but my new setup with the same client > > codebase is now failing. > > > > It seems like there might be something wrong with the OAuth tokens > > being issued, but that seems kinda crazy that there could be a problem > > that widespread. > > > > -damon >
