Hey Matt, Yep, I'm passing oauth_callback - and it does look like that's the problem, because I have another app which doesn't send it, and it's working fine.
Is this by design, or will it be changed back? I don't need it to use the oauth_callback url that I pass, but it'd be good to return to the specified callback URL by default. Thanks, Elliott On Jun 9, 11:17 pm, Matt Sanford <m...@twitter.com> wrote: > Hi there, > > Are you by chance passing anything in to the request_token call > for the value of oauth_callback? I checked out a few other services > and they seemed fine. If you're sending oauth_callback=oob (a.k.a. > "out of band") then the system is forced into the PIN flow. We're > working on docs for all of this now but let me know if that's what > you're sending. > > — Matt > > On Jun 9, 2009, at 2:55 PM, Keith Hanson wrote: > > > > > > > Same here, actually, for tweetingtoohard.com (tried to post here > > before but it looks like it got eaten :P) > > > We've put up a snarky message in the meantime about the blunders :P > > But please do correct us if we have done something incorrect. > > > -- Keith Hanson > > @big_love > > keith (at) tweetingtoohard.com > > > On Jun 9, 4:47 pm, Elliott Kember <elliott.kem...@gmail.com> wrote: > >> Hey guys, > > >> I'm having a few problems with the OAuth API and my browser-based app > >> - it's giving me PIN numbers at the /oauth/authorize page, even > >> though > >> it's set to return to a callback in the OAuth settings - I've > >> rechecked my settings, and the application is definitely set as a > >> browser app. > > >> I'm guessing this is something to do with the new PIN-based desktop > >> app code, just wondering when it'll be fixed - or whether I'm doing > >> something wrong! > > >> Thanks, > >> Elliott
