Question

I’ve been using the Twitter gem in my latest Rails app, and so far have had no problems. I’ve registered the app, have set the API tokens in config/initializers/twitter.rb, and have tested that it works in a custom rake test that requires the gem. The problem, however, is that when I try to send a tweet form a controller, nothing happens. My initializer looks like so:

require 'twitter'

Twitter.configure do |config|
  config.consumer_key = '###'
  config.consumer_secret = '###'
  config.oauth_token = '###'
  config.oauth_token_secret = '###'
end

The ### are filled in correctly in my app, obviously. In my rake file, I require the gem at the top of the file, and am then able to send a test tweet with Twitter.update(tweet) however, the same syntax does not work from my controllers.

What am I doing wrong here? Do I need to re-initialize the gem from the controller?

Answer 1

After some tinkering, this is the simple solution:

@twitter = Twitter::Client.new
@twitter.update(tweet)

Adding that to my controller method worked perfectly, since the Twitter client had already been authenticated when the app started. This is the app sending out tweets, by the way, not users sending tweets through the app, so I didn’t need to re-authenticate.