Oauth doesn't work in Ruby 2

[jroes]

I'm guessing this has something to do with the black magic going on in the custom rdio-simple oauth stuff.

› rdio user
error: 795: unexpected token at '<h1>403 Developer Inactive</h1>'

This probably belongs upstream with rdio-simple, but maybe this project should just use a normal oauth gem instead of rdio-simple altogether.

[pengwynn]

D'oh. Will try to dig into this. I was trying to avoid the weight of the OAuth gem, but we might have to bite the bullet.

[shawnbro]

Has this issue been resolved? I am trying to authenticate with Rdio API using ruby library and still getting the "Developer Inactive" error...

[pengwynn]

I'm unable to reproduce using Ruby 2 and a fresh install of the latest version of the rdio-cli gem. Is your key active on Mashery? http://rdio.mashery.com/apps/mykeys

[lodestone]

FWIW I first saw this issue, then I started seeing my name returned with rdio user. I'm still seeing the following issue on my system across several ruby versions. Not sure if it is related or not.

 matt@zo-2  ~/Music ‹1.9.3-p547›
 • rdio user 
 Matt Petty
 matt@zo-2  ~/Music ‹1.9.3-p547›
 • rdio play
 15:19: execution error: The variable play is not defined. (-2753)

[pengwynn]

@lodestone Thanks for the feedback. Can you share your version of Rdio and OSX?

[lodestone]

@pengwynn Yosemite, rdio 1.2.2

[pengwynn]

I wonder if the AppleScript interface changed in v2. I'm on Rdio 2.3.6. Is upgrading an option?

[lodestone]

I'm on Rdio 2.36 - My mistake - I thought you were asking for the rdio-cli version. And you asking about the Rdio version made me realize - I need to have the native app running. Duh. I've been running rdio web version with Fluid so I actually forgot I even had a native app of Rdio.

Anyway - it's "fixed" now.

Cheers