I was just about to ask the exact same question. I noticed this soon after implementing oauth in Hahlo4 but figured it was just a bug in my code. I'd auth on my laptop and it would work fine, then I'd auth on my phone and the laptop would stop working, auth back on the laptop and the phone would stop working etc etc.
* heads off to read the google code ticket * On Mar 23, 11:32 am, Abraham Williams <[email protected]> wrote: > I submitted this to the issue queue since this is a big problem for people > with multiple > computers:http://code.google.com/p/twitter-api/issues/detail?id=372 > > > > On Sat, Mar 21, 2009 at 21:46, Chen Jie <[email protected]> wrote: > > > I got the same problem, but it seems the access token is not invalid > > immediately, I am developing a web app, and I authorize my account > > access for my local development environment and deploy environment, > > the early access token will be invalid in server hours. > > > Though this problem is not an issue for me, but it exactly impact > > desktop apps which can use several places and do not have user > > identification. > > > -- > > chenyuejie > >http://twittergadget.appspot.com/ > > > On Mar 22, 3:54 am, Joshua Perry <[email protected]> wrote: > > > I've been going through testing OAuth with my desktop application on my > > > laptop and on my desktop computer. I noticed that when I get an > > > AccessToken with my laptop, my desktop then starts getting 401 > > > unauthorized errors and vice versa. I'm not able to have the same > > > application authorized on two computers simultaneously. > > > > Is this a bug or is there a way around this? The only way I can think > > > to get around the limitation is to somehow transfer the good AccessToken > > > from one computer to any others that I want to use my application on. > > > Perhaps some out-of-band mechanism that I provide on my own website to > > > allow a user's application to get their currently active AccessToken, > > > though I'm not sure this is a service that I'm prepared to support. > > > > I'm not sure how I expect Twitter to react to a second AccessToken > > > request for an application when one already exists, but currently it > > > seems to just replace the current one and only allows a single active > > > AccessToken per application. This seems to only be a limiting factor for > > > desktop applications. > > > > Perhaps storing and allowing up to 3 or 4 active AccessTokens per > > > application would be sane. > > -- > Abraham Williams |http://the.hackerconundrum.com > Web608 | Community Evangelist |http://web608.org > This email is: [ ] blogable [x] ask first [ ] private. > Sent from: Madison Wisconsin United States.
