[twitter-dev] OAuth pin flow happening instead of normal oauth_callback redirect

2010-09-01 Thread Damon Clinkscales
I have a sample app which works fine on my local machine. When I deploy it to a dev server and go through the flow, I get the PIN in the browser and no redirect. I checked the server timestamps and they are within 1 second of each other. Does anyone have any thoughts on what might be wrong? I

Re: [twitter-dev] OAuth pin flow happening instead of normal oauth_callback redirect

2010-09-01 Thread Taylor Singletary
Hi Damon, Verify that your application has a default callback URL set on your app's page on dev.twitter.com -- the existence of that field is what determines whether we'll automatically be sending you into out of band mode or note. Further, while that default callback URL needs to exist on your

Re: [twitter-dev] OAuth pin flow happening instead of normal oauth_callback redirect

2010-09-01 Thread Damon Clinkscales
On Wed, Sep 1, 2010 at 3:25 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Damon, Verify that your application has a default callback URL set on your app's page on dev.twitter.com -- the existence of that field is what determines whether we'll automatically be sending you into

Re: [twitter-dev] OAuth pin flow happening instead of normal oauth_callback redirect

2010-09-01 Thread Taylor Singletary
Great. I'll take a look at the most recent version of the ruby gem as soon as I get a chance. From my experience, 0.3.4 was a very solid release. I'll follow up when I've had a chance to review. Thanks, Taylor On Wed, Sep 1, 2010 at 2:38 PM, Damon Clinkscales sca...@pobox.com wrote: On Wed,