When I saw your mail I quickly restested some of my apps and they all
continue to work fine with twitter oauth (using rails, see
This doesn't appear to have been a general problem with the service itself -
suggest you look more at whatever libraries/plugins/dev environment are you
using for twitter oauth, and your app configuration. I think you can get the
PIN flow if either (a) callback url not provided properly or (b) app is not
registered as a "browser" app indicating it will use twitter for
On Fri, Aug 14, 2009 at 12:09 AM, joelmoss <j...@developwithstyle.com>wrote:
> I'm getting the same issues too. Keeps giving me the pin instead of
> redirecting to my callback. Anyone get this resolved?
> On Aug 12, 9:52 pm, Eric Waller <erwal...@gmail.com> wrote:
> > I'm having the same problem--getting aPINinstead 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 <corgan1...@gmail.com> 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 digitPIN!
> > > "You've successfully granted access to . Simply return to and enter
> > > the followingPINto complete the process. 1234567"
> > > According to this articlehttp://
> > > 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?