manlycode
0.1.8 breaks Twilio support - Twilio::REST::RequestError: Authenticate
Hi,
I've been using this gem for at least several months and like it a lot. Thanks for supplying it!
Like the other open issue, upgrading from 0.1.7 to 0.1.8 (and 0.1.9) broke Twilio support for me, but the error was different.
This is what I got: Twilio::REST::RequestError: Authenticate
Googling around it appears that my cucumber tests are actually trying to communicate with Twilio, i.e. the sms-spec gem is not intercepting the communication attempt like it has always done in the past. And the stack trace bears that out: nowhere does sms-spec appear.
When I freeze the gem at 0.1.7 everything works fine.
Hopefully someone can fix this.
Thanks, Larry
If you're using an older version of the twilio-ruby gem, sms-spec will break. I'm working in restructuring SMS-spec to work with different versions of the twilio-ruby gem. But in the meantime, locking the version down will be the best solution. — Sent from Mailbox for iPhone
On Fri, Apr 18, 2014 at 5:42 PM, larryh [email protected] wrote:
Hi, I've been using this gem for at least several months and like it a lot. Thanks for supplying it! Like the other open issue, upgrading from 0.1.7 to 0.1.8 (and 0.1.9) broke Twilio support for me, but the error was different. This is what I got: Twilio::REST::RequestError: Authenticate Googling around it appears that my cucumber tests are actually trying to communicate with Twilio, i.e. the sms-spec gem is not intercepting the communication attempt like it has always done in the past. And the stack trace bears that out: nowhere does sms-spec appear. When I freeze the gem at 0.1.7 everything works fine. Hopefully someone can fix this. Thanks,
Larry
Reply to this email directly or view it on GitHub: https://github.com/manlycode/sms-spec/issues/5
Hi,
Thanks for the quick reply. I'm using the latest version of twilio-ruby: 3.11.5, so I don't know what the problem could be. Is there anything you'd like me to try or to send you?