I'm having the same problem--getting a PIN instead of being redirected at the end of the oauth flow. My application is set as a browser-type app, and I'm providing a callback url.
Everything was working as expected for the past couple of weeks, the problem started when the API became available again after the ddos. On Aug 12, 10:56 am, Tony Amoyal <[email protected]> wrote: > I am implementing some ruby on rails code tweet stuff for my users. I > am creating the proper oauth link...something like > > http://twitter.com/oauth/authenticate?oauth_token=y2RkuftYAEkbEuIF7zK... > > but Twitter redirects the user to oauth/authorize after he clicks > "Allow" which then gives him the 7 digit PIN! > > "You've successfully granted access to . Simply return to and enter > the following PIN to complete the process. 1234567" > > According to this articlehttp://apiwiki.twitter.com/Sign-in-with-Twitter > > Twitter should be redirecting the user to the callback URL I provided > in the application settings when I hit the /oauth/authenticate path > because that is saying that I am now a Desktop or iPhone app. Does > anyone know why this is happening?
