Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

uninitialized constant Twitter::REST #479

Closed
NARKOZ opened this issue Nov 2, 2013 · 6 comments
Closed

uninitialized constant Twitter::REST #479

NARKOZ opened this issue Nov 2, 2013 · 6 comments

Comments

@NARKOZ
Copy link

NARKOZ commented Nov 2, 2013

No description provided.

@NARKOZ NARKOZ closed this as completed Nov 2, 2013
@sferik
Copy link
Owner

sferik commented Jul 13, 2014

You are using an outdated version of the gem. Please update to version 5.0.0 or greater.

@senych-vitalii
Copy link

same problem with gem 'twitter', '~> 5.11.0'
Result of investigation: I have installed two gems https://github.com/sferik/twitter and https://github.com/twitter/twitter-text-rb, they both have 'Twitter' as main module and when I call Twitter, I reached second instead first...

@sagarjunnarkar
Copy link

What is solution on this? Please update...

@senych-vitalii
Copy link

I did next: forked 'twitter-text' gem, rename 'Twitter' module to 'TwitterText', change it in all submodules inside gem, linked 'twitter-text' gem to my repository in 'Gemfile' (gem 'twitter-text', github: 'name/twitter-text-rb'), start using it like 'TwitterText' module and 'Twitter' gem as 'Twitter' module.
This solve problem for me. But onse more - it happend only when I started using two 'twitter-text' and 'twitter' gems.

@ghost
Copy link

ghost commented Oct 7, 2014

I don't use twitter text gem and my version is 5.11..still happens to me

@NARKOZ NARKOZ reopened this Feb 3, 2015
@stve
Copy link
Collaborator

stve commented Feb 3, 2015

@NARKOZ presumably you re-opened this for a reason. If you are still having an issue with this, please post a Gemfile (and potentially a link to your Gemfile.lock) as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants