uninitialized constant Twitter::REST #878

cheater · 2017-11-09T15:24:10Z

Assuming this got fixed in #479 and reared its head due to some other issue now.

I literally only installed ruby 2.4, then did gem install t, and this is what happened.

Traceback:

/var/lib/gems/2.4.0/gems/t-3.1.0/lib/t/cli.rb:82:in `authorize': uninitialized constant Twitter::REST::Client::BASE_URL (NameError)
	from /var/lib/gems/2.4.0/gems/thor-0.20.0/lib/thor/command.rb:27:in `run'
	from /var/lib/gems/2.4.0/gems/thor-0.20.0/lib/thor/invocation.rb:126:in `invoke_command'
	from /var/lib/gems/2.4.0/gems/thor-0.20.0/lib/thor.rb:387:in `dispatch'
	from /var/lib/gems/2.4.0/gems/thor-0.20.0/lib/thor/base.rb:466:in `start'
	from /var/lib/gems/2.4.0/gems/t-3.1.0/bin/t:20:in `<top (required)>'
	from /usr/local/bin/t:23:in `load'
	from /usr/local/bin/t:23:in `<main>'

gem list says:

*** LOCAL GEMS ***

addressable (2.5.2)
bigdecimal (1.3.2, default: 1.3.0)
buftok (0.2.0)
domain_name (0.5.20170404)
equalizer (0.0.11)
geokit (1.11.0)
htmlentities (4.3.4)
http (3.0.0)
http-cookie (1.0.3)
http-form_data (2.0.0)
http_parser.rb (0.6.0)
io-console (default: 0.4.6)
json (2.1.0, default: 2.0.4)
launchy (2.4.3)
memoizable (0.4.2)
multipart-post (2.0.0)
naught (1.1.0)
oauth (0.5.3)
openssl (2.0.6, default: 2.0.5)
psych (2.2.4, default: 2.2.2)
public_suffix (3.0.1)
rdoc (5.1.0, default: 5.0.0)
retryable (2.0.4)
simple_oauth (0.3.1)
t (3.1.0)
thor (0.20.0)
thread_safe (0.3.6)
twitter (6.2.0)
unf (0.1.4)
unf_ext (0.0.7.4)

Not sure how to progress. Workarounds?

The text was updated successfully, but these errors were encountered:

cheater · 2017-11-09T15:55:20Z

Tried this in ruby 2.1 as well, with same result.

elliotblackburn · 2017-11-10T17:43:43Z

I'm getting the same issue, not quite sure what to do either. My ruby version is ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16].

It seems to be failing to find a constant in the twitter library, it's looking in Twitter::REST::Client but from what I can see in the file - https://github.com/sferik/twitter/blob/d7951759da897e6a8e3ed0069b2e850470991e3f/lib/twitter/rest/client.rb it's not there. It seems to actually be in Twitter::REST::Request I believe?

elliotblackburn · 2017-11-10T17:46:27Z

Ah I see the issue - v6.1.0...v6.2.0 BASE_URL used to reside in that file but has been moved. So when Twitter 6.2.0 was released, versions of this are breaking.

Any chance someone could fix the version to 6.1.0 so this library will continue working? I'm not a huge ruby expert, you'd also need publish access.

gtramontina · 2017-11-14T11:03:40Z

Yeah, I guess if moving the constant out to a different location was a deliberate move, then this should be flagged as a breaking change, thus a major release should've been released. Got here from getting the same error when running a fresh install of https://github.com/sferik/t (gem install t).

I'd suggest unpublishing v6.2.0 (gem yank?) and republishing it as v7.0.0.

sferik · 2017-11-18T22:12:30Z

I’m working on a fix for this issue now. Sorry for the trouble.

elliotblackburn · 2017-11-23T13:39:29Z

Thanks @sferik, looking forward to being able to use the CLI client 👍

ghost · 2017-11-30T05:52:57Z

Thank you for working on this, waiting on it :D

garybunofsky · 2017-12-01T00:26:33Z

Patiently waiting for this fix as well. Thanks for working on it! 👍

ghamarian · 2017-12-03T14:09:06Z

Also waiting :-) Thanks!

chrisvoncsefalvay · 2017-12-04T11:29:09Z

Also waiting. Thanks for working on this! 👍

vuiermark · 2017-12-04T21:32:11Z

waiting here as well...thanks!

cheater · 2017-12-05T17:30:31Z

OK guys i know you're impatient but this nagging absolutely has to stop. I get retarded "bump" notifications every day. This isn't goddamn twitter. Go live out your ADHD over there. The guy obviously hasn't been on github since november - look at his activity - so what are you trying to achieve with this? He's busy with his real life (yeah, some people have one) and is going to get around to it... WHEN HE GETS AROUND TO IT. Stop nagging or I'll close the bug report!

rvagg · 2017-12-06T17:41:56Z

Here's your workaround folks: edit /Library/Ruby/Gems/2.3.0/gems/t-3.1.0/lib/t/cli.rb, or maybe /Library/Ruby/Gems/*/gems/t-*/lib/t/cli.rb if you don't have that file. Replace the two instances of Twitter::REST::Client::BASE_URL with Twitter::REST::Request::BASE_URL and you're good to go.

rdmarsh · 2017-12-12T00:28:49Z

expanding on @rvagg: ubuntu 17.10, file was located at /var/lib/gems/2.3.0/gems/t-3.1.0/lib/t/cli.rb

hexwaxwing · 2017-12-18T19:22:59Z

expanding on @rvagg: OS X 10.12.6 w/ rvm, file was located at ~/.rvm/gems/ruby-2.4.3/gems/t-3.1.0/lib/t/cli.rb

…uby#878)

DavidCWGA · 2018-04-25T03:24:25Z

rvagg's workaround doesn't work for me. The error changes to:

/var/lib/gems/2.3.0/gems/t-3.1.0/lib/t/rcfile.rb:89:in `profiles': undefined method `[]' for false:FalseClass (NoMethodError)

jm3 · 2018-05-19T20:55:30Z

@sferik would love some help getting this fixed so i can use t again!

fuzz · 2018-05-29T18:05:28Z

It's not the prettiest solution, but if anyone just wants to get this working you can do it with bundler: Make a Gemfile with gem "t" and gem "twitter", "6.1.0", call bundle install and then run it with bundle exec t

ialexs · 2018-06-21T06:35:21Z

Also not the prettiest solution:
I copy the .twurlrc (from Twurl https://github.com/twitter/twurl) to .trc
then run t as usual.

cheers

jasonhemann · 2018-06-25T15:39:39Z

@fuzz or @ialexs, could either of you describe these two solutions in a little more detail?

I didn't see .twurlrc in the Twurl repo, and I don't know that I have bundle installed. I'm not familiar with that tool, and the name seems pretty Google-proof.

Thanks,

DelphicOkami · 2018-06-29T09:19:23Z

@jasonhemann

Go to https://apps.twitter.com/
Ensure your app (whether newly created or otherwise) has Read, Write and Access direct messages permissions
Locally run gem install twurl
Run twurl authorize --consumer-key {YOUR APP'S CONSUMER KEY} --consumer-secret {YOUR APP'S CONSUMER SECRET}
Follow the steps it requests that you do
Copy ~/.twurlr to ~/.trc

Essentially what @ialexs seems to mean is, copy the file generated by twurl

DelphicOkami · 2018-06-29T09:20:08Z

The above totally worked for me

cprkrn · 2018-07-11T04:37:53Z

Ah editing the cli.rb worked fine! Didn't realize there were two instances. Many thanks.

kylejohnston · 2018-07-14T05:04:00Z

The path to my cli.rb file was listed in the error message output after I entered my API keys (my path was different from the paths listed above).

Once I edited both instances of Twitter::REST::Request::BASE_URL, the installation completed.

albill · 2018-07-19T02:33:26Z

Really, this has been broken for eight months without a fix? WTH?

eobrain · 2018-07-23T03:14:25Z

Let's be nice here. This is a 12-year old open-source project. It is not unreasonable that the original maintainer might not jump in and fix bugs after all that time.

Anyone with Ruby skills and sufficient interest could contribute a fix. (I myself actually spent a little while freshening my rusty Ruby skills to see if I could fix this issue, but I just have not had time to devote to it.)

166 people have contributed to this repo over the years, so I suspect there are multiple people out there who would be able and willing to fix this.

jm3 · 2018-07-24T16:25:13Z

@eobrain any suggestions for how best to appeal to some of those people?

kennethreitz · 2018-08-29T08:31:50Z

For those just running into this issue (like myself), this solution worked for me.

thebitstick · 2018-12-14T05:03:57Z

Holy shit happy new year.
Also having this issue.
When is a fork coming to Rubygem that will be maintained, jesus.

patwalls · 2019-04-02T06:30:39Z

This bug totally sucks, spent a ton of time trying all these solutions and none worked. Are there any alternatives to the twitter ruby gem?

cognitive137 · 2019-06-16T13:06:33Z

@jasonhemann

Go to https://apps.twitter.com/

Ensure your app (whether newly created or otherwise) has Read, Write and Access direct messages permissions

Locally run gem install twurl

Run twurl authorize --consumer-key {YOUR APP'S CONSUMER KEY} --consumer-secret {YOUR APP'S CONSUMER SECRET}

Follow the steps it requests that you do

Copy ~/.twurlr to ~/.trc

Essentially what @ialexs seems to mean is, copy the file generated by twurl

@jasonhemann

Go to https://apps.twitter.com/

Ensure your app (whether newly created or otherwise) has Read, Write and Access direct messages permissions

Locally run gem install twurl

Run twurl authorize --consumer-key {YOUR APP'S CONSUMER KEY} --consumer-secret {YOUR APP'S CONSUMER SECRET}

Follow the steps it requests that you do

Copy ~/.twurlr to ~/.trc

Essentially what @ialexs seems to mean is, copy the file

I now get this error:

/Library/Ruby/Gems/2.3.0/gems/twurl-0.9.3/lib/twurl/cli.rb:94:in parse_options': invalid option: --8yZ1Sso8SKsPJG7F0BYMT62QG (OptionParser::InvalidOption) from /Library/Ruby/Gems/2.3.0/gems/twurl-0.9.3/lib/twurl/cli.rb:17:in run'
from /Library/Ruby/Gems/2.3.0/gems/twurl-0.9.3/bin/twurl:4:in <top (required)>' from /usr/local/bin/twurl:22:in load'
from /usr/local/bin/twurl:22:in `

'

elliotblackburn · 2019-06-16T21:26:11Z

@cognitive137 I think you should probably reset/delete that API key as it looks like it's been printed out in your error log there. (Editing your github comment will not remove it as there is a history of comments avalible). You should do this asap or someone may be able to use twitter as you 😢

cognitive137 · 2019-06-17T04:42:22Z

@BlueHatbRit , thank you!

DennisFaucher · 2019-12-15T23:07:04Z

@jasonhemann

Go to https://apps.twitter.com/

Ensure your app (whether newly created or otherwise) has Read, Write and Access direct messages permissions

Locally run gem install twurl

Run twurl authorize --consumer-key {YOUR APP'S CONSUMER KEY} --consumer-secret {YOUR APP'S CONSUMER SECRET}

Follow the steps it requests that you do

Copy ~/.twurlr to ~/.trc

Essentially what @ialexs seems to mean is, copy the file generated by twurl

That's the fix! Many thanks @jasonhemann

bnsv · 2019-12-22T15:31:04Z

@jasonhemann

1. Go to https://apps.twitter.com/

2. Ensure your app (whether newly created or otherwise) has Read, Write and Access direct messages permissions

3. Locally run `gem install twurl`

4. Run `twurl authorize --consumer-key {YOUR APP'S CONSUMER KEY} --consumer-secret {YOUR APP'S CONSUMER SECRET}`

5. Follow the steps it requests that you do

6. Copy ~/.twurlr to ~/.trc

Essentially what @ialexs seems to mean is, copy the file generated by twurl

It's works for me too. You missing c on the last command (should be cp ~/.twurlrc ~/.trc). Thank you.

BitumFelix · 2021-01-06T23:25:22Z

Here's your workaround folks: edit /Library/Ruby/Gems/2.3.0/gems/t-3.1.0/lib/t/cli.rb, or maybe /Library/Ruby/Gems/*/gems/t-*/lib/t/cli.rb if you don't have that file. Replace the two instances of Twitter::REST::Client::BASE_URL with Twitter::REST::Request::BASE_URL and you're good to go.

This worked for me too!
I was almost giving up.

cmdrfletcher · 2021-04-18T13:31:38Z

@jasonhemann

Go to https://apps.twitter.com/

Ensure your app (whether newly created or otherwise) has Read, Write and Access direct messages permissions

Locally run gem install twurl

Run twurl authorize --consumer-key {YOUR APP'S CONSUMER KEY} --consumer-secret {YOUR APP'S CONSUMER SECRET}

Follow the steps it requests that you do

Copy ~/.twurlr to ~/.trc

Essentially what @ialexs seems to mean is, copy the file generated by twurl

This is still working! Thanks! 👏

techieshark mentioned this issue Feb 24, 2018

Fix version dependencies and fix tests sferik/t-ruby#386

Closed

fenhl added a commit to fenhl/syncbin that referenced this issue Feb 24, 2018

Remove completion for t since t is currently broken (sferik/twitter-r…

5b1a7f3

…uby#878)

wayne5540 mentioned this issue Jun 11, 2018

`authorize': uninitialized constant Twitter::REST::Client::BASE_URL (NameError) sferik/t-ruby#402

Open

compuguy mentioned this issue Mar 22, 2019

New release required sferik/t-ruby#388

Open

riclage mentioned this issue Jan 16, 2021

Please let us know if this is no longer supported so we won't bother you with issues :) sferik/t-ruby#420

Open

AntZoo mentioned this issue Nov 2, 2021

Error after entering API Key and API Secret Key sferik/t-ruby#451

Open

cllns mentioned this issue Apr 1, 2022

uninitialized constant Twitter::REST::Client::BASE_URL (NameError) sferik/t-ruby#458

Open

steinerkelvin mentioned this issue Apr 30, 2022

authorizing t (2022-04-30) steinerkelvin/twitter-relationships#1

Open

Wirone mentioned this issue Mar 2, 2023

Does this work anymore? sferik/t-ruby#459

Open

sferik closed this as completed Sep 19, 2023

uninitialized constant Twitter::REST #878

uninitialized constant Twitter::REST #878

Comments

cheater commented Nov 9, 2017 • edited Loading

cheater commented Nov 9, 2017

elliotblackburn commented Nov 10, 2017

elliotblackburn commented Nov 10, 2017

gtramontina commented Nov 14, 2017

sferik commented Nov 18, 2017

elliotblackburn commented Nov 23, 2017

ghost commented Nov 30, 2017

garybunofsky commented Dec 1, 2017

ghamarian commented Dec 3, 2017

chrisvoncsefalvay commented Dec 4, 2017

vuiermark commented Dec 4, 2017

cheater commented Dec 5, 2017

rvagg commented Dec 6, 2017

rdmarsh commented Dec 12, 2017

hexwaxwing commented Dec 18, 2017

DavidCWGA commented Apr 25, 2018 • edited Loading

jm3 commented May 19, 2018

fuzz commented May 29, 2018 • edited Loading

ialexs commented Jun 21, 2018

jasonhemann commented Jun 25, 2018

DelphicOkami commented Jun 29, 2018 • edited Loading

DelphicOkami commented Jun 29, 2018

cprkrn commented Jul 11, 2018 • edited Loading

kylejohnston commented Jul 14, 2018

albill commented Jul 19, 2018

eobrain commented Jul 23, 2018

jm3 commented Jul 24, 2018

kennethreitz commented Aug 29, 2018

thebitstick commented Dec 14, 2018 • edited Loading

patwalls commented Apr 2, 2019

cognitive137 commented Jun 16, 2019

elliotblackburn commented Jun 16, 2019

cognitive137 commented Jun 17, 2019

DennisFaucher commented Dec 15, 2019

bnsv commented Dec 22, 2019

BitumFelix commented Jan 6, 2021

cmdrfletcher commented Apr 18, 2021

cheater commented Nov 9, 2017 •

edited

Loading

DavidCWGA commented Apr 25, 2018 •

edited

Loading

fuzz commented May 29, 2018 •

edited

Loading

DelphicOkami commented Jun 29, 2018 •

edited

Loading

cprkrn commented Jul 11, 2018 •

edited

Loading

thebitstick commented Dec 14, 2018 •

edited

Loading