Having a problem with the twitter_oauth gem. It seems to work fine for the
update method and others, e.g.
chan = Jobchannel.find(:last, :conditions => ['access_token IS NOT NULL'])
client = TwitterOAuth::Client.new(
:consumer_key => SAFETWEET_CONSUMER_KEY,
:consumer_secret => SAFETWEET_CONSUMER_SECRET,
:token => chan.safetweet_access_token,
:secret => chan.safetweet_access_secret
)
ret = client.update('test')
but when I use the update profile method, I get this:
ret = client.update_profile(:description => 'test')
JSON::ParserError: 665: unexpected token at '<?xml version="1.0"
encoding="UTF-8
<hash>
<request>/1/account/update_profile</request>
<error>Could not authenticate with OAuth.</error>
</hash>
'
from
/home/deploy/.gem/ruby/1.8/gems/json_pure-1.2.2/lib/json/common.rb:
from
/home/deploy/.gem/ruby/1.8/gems/json_pure-1.2.2/lib/json/common.rb:
from
/opt/ruby/lib/ruby/gems/1.8/gems/twitter_oauth-0.4.3/lib/twitter_oa
from
/opt/ruby/lib/ruby/gems/1.8/gems/twitter_oauth-0.4.3/lib/twitter_oa
from (irb):12
Any ideas?
Thanks,
Gary Zukowski
TweetMyJOBS.com
@garyzukowski
@tweetmyjobs
LinkedIn <http://www.linkedin.com/profile/view?id=414054>
704-544-9370
Listen to the TweetMyJOBS Holiday Album at http://www.tweetmyjobs.com/album
Check out TweetMyJOBS on MSNBC's Dylan Ratigan Show:
http://www.msnbc.msn.com/id/31510813/#39313587
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please notify the system manager.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee, you should not
disseminate, distribute or copy this email. Please notify the sender
immediately by email if you have received this email by mistake and delete
this email from your system. If you are not the intended recipient, you are
notified that disclosing, copying, distributing or taking any action in
reliance on the contents of this information is strictly prohibited.
From: Dean Collins [mailto:[email protected]]
Sent: Wednesday, January 05, 2011 11:00 AM
To: [email protected]
Subject: [twitter-dev] RE: New twitter in ie8 broken again
Huh well that IS interesting.
I have no idea why but someone just emailed me to answer my question about
New Twitter being broken for IE8.
They told me if you turn on "InPrivate" browsing on IE8 that new twitter
works.. Just tried it for my account http://www.Twitter.com/LiveNascarChat
.... came up perfect.
Can someone from twitter explain what in their code broke this morning at
8am that is negated by inprivate browsing?
Cheers,
Dean
_____
From: Dean Collins
Sent: Wednesday, January 05, 2011 8:23 AM
To: [email protected]
Subject: New twitter in ie8 broken again
New twitter in ie8 is broken again, works great in firefox but started
failing in ie8 about 8am this morning.
Cheers,
Dean
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
