Got it fixed. I just set my rails app to use 0.6.12 of the twitter
gem.
On Aug 14, 1:09 am, Eric Waller wrote:
> If you're using the twitter rubygem, the problem is detailed
> herehttp://groups.google.com/group/ruby-twitter-gem/browse_thread/thread/
>
> Basically the twitter gem isn't using
If you're using the twitter rubygem, the problem is detailed here
http://groups.google.com/group/ruby-twitter-gem/browse_thread/thread/6e935089d55a92c2.
Basically the twitter gem isn't using the newest oauth gem properly,
and using an older version of the oauth gem seems to fix everything.
Hopefu
Hi Joel,
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
http://tardate.blogspot.com/2009/06/using-twitter-oauth-with-rails-sample.html).
This doesn't appear to have been a general problem with the service itself -
su
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 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 brow
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 ag
