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

Unitialized Constant Twilio::REST Sending SMS From a model #35

Closed
kcollignon opened this issue Feb 1, 2013 · 4 comments
Closed

Unitialized Constant Twilio::REST Sending SMS From a model #35

kcollignon opened this issue Feb 1, 2013 · 4 comments

Comments

@kcollignon
Copy link

Hello,
I am having trouble sending an SMS from my Rails app. It works fine locally, but on production I am getting:

unitialized constant Twilio::REST

This is my app/models/alert.rb directory. Obviously putting the sending functionality at the controller level would help, but any ideas on how to have it recognize this in the model? I have some tricky recipient scoping/mapping which is why it is in the model. Thanks!

@kcollignon
Copy link
Author

FWIW i tried doingg the same thing in the Controller and get the same error.

@kevinburke
Copy link
Contributor

Hi Kevin,
That's odd, and I'm sorry to hear you're having trouble. It's possible your local install has a module or two that your production environment doesn't. Could you post a little bit of the surrounding code? Is there a way to do gem list or something in your local and your production environments?

@andrewmbenton
Copy link
Contributor

it seems like this might be a problem of only requiring the twilio-ruby gem in an initialization file for the local environment.

@dougblack
Copy link
Contributor

Hi @kcollignon! I'm going to go ahead and close since it's been a while since the last person commented on this issue.

If you're still having trouble feel free to reopen!

Ragil added a commit that referenced this issue Dec 9, 2015
Make nbf optional in Access Tokens
ajtack pushed a commit to ajtack/twilio-ruby that referenced this issue Apr 28, 2017
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

4 participants