-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
757: unexpected token #490
Comments
Any particular reason you’re using version 5.0.0.rc.1 instead of 5.0.0 final? Can you please try to reproduce the issue with the final gem? It would also be helpful to know the patch level of your Ruby version. |
Yes and no. The as-yet-unreleased update to |
No particular reason, actually. I hadn't noticed you had released 5.0.0 final. Guess I should have checked, sorry. I'll upgrade to 5.0.1 (which I think you released today). As for the Ruby patch level, I'm currently on ruby-2.0.0-p247 but I know that there was a new patch released to address some security concern, so I'll also try to upgrade to that new version. |
Please reopen this issue if 5.0.1 doesn’t fix the problem. |
Just wanted to let you know that everything's running smoothly now. 👏 |
When using the
Twitter::Streaming::Client
, I get this error when the json gem tries to parse some tweets. As an example, a tweet with the id404911776141037568
threw this error. However, I can't reproduce it by callingclient.status(404911776141037568)
with theTwitter::REST::Client
. Is there a difference between the way a tweet is parsed with the Streaming and Rest clients?Stack trace here.
The text was updated successfully, but these errors were encountered: