When you wen through the OAuth flow on the first computer Twitter saved the access tokens that your app received. When you authenticated with the second computer the access tokens from the first computer that Twitter stored wore replaced. Now the first computer has invalid access tokens. This is a know issue and Twitter is working on a) multiple access tokens per user per application or b) resending the original access tokens for later. Not sure which they will decide to do.
It would also probably be good to let your users know if the status was succesfully posted or not. Abraham On Wed, Apr 15, 2009 at 15:47, Ahmed R <[email protected]> wrote: > > Hello, > > I am working on my app and have implemented it using oAuth for login. > For the most part its going quite well until I ran into a problem > today. Before I begin, the way Im using oAuth is as follows: > > 1 - The user can browse around most of the site without having to log > in. > > 2 - If they want to update their status they click on the log in > button which takes them through the oAuth flow. > > 3 - I grab the token information and save it in a session. I do not > store it in a DB since I dont have a real need for that. > > 4 - I use the token data to allow the user to update their status from > my site. The session is used to keep the user logged in around the > site. > > The problem: > > 1 - I was logged in and everything seemed normal. > > 2 - When I updated the status, the process seemed to be fine as it > normally is, but the status never got updated on Twitter. > > 3 - I tried over a period of time and the status never got updated. > > 4 - I was using another computer and tried it and it worked. On that > second computer, I logged in first > > 5 - Back to the original computer, I tried again to update the status > and it still did not work. > > 6 - Then on the original computer I logged out then logged back in and > updating the status finally worked. > > So although it appeared on my site that I was logged in and it > appeared to me that everything was fine, it did not work. I had to log > out (clear my session) then log back in to get it to work. > > Im assuming this has something to do with the session, however I > really have no idea what couldve caused that. A couple points, this > is the first time this has happened. Also I had the browser open over > night. > > Any ideas? > -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, Wisconsin, United States
