Closed pushups closed 9 years ago
Burgestrand
commented
9 years ago Did you happen to download the non-binary application key? I get the same kind of error if I use the C code application key (textfile), instead of the binary application key.
PS: Could you please format the crash report with a code block? Would make your post a bit easier to navigate. :)
pushups
commented
9 years ago Hi! I downloaded the binary application key and copied it into the examples directory.
examples $ file spotify_appkey.key
spotify_appkey.key: dataLet me know if any other information would be useful.
Burgestrand
commented
9 years ago When you get the original output from the terminal, you also see (as part of the trace) which libspotify function it called before it segfaulted, but since you got no output before segfault (I believe?) I'm assuming it was when it was creating the session.
Segfaulting when creating the session tend to be for a few different reasons:
I'm still leaning towards the bad application key. What is the size of your application key file?
$ wc -c spotify_appkey.key
? spotify_appkey.keyYou're right it is during session create:
-- C level backtrace information -------------------------------------------
0 ruby 0x000000010d91d9a0 rb_vm_bugreport + 144
1 ruby 0x000000010d7d1281 report_bug + 305
2 ruby 0x000000010d7d1144 rb_bug + 180
3 ruby 0x000000010d89fd0c sigsegv + 156
4 libsystem_platform.dylib 0x00007fff8cbe55aa _sigtramp + 26
5 universal-darwin 0x000000010e3648c6 sp_session_create + 106
6 ??? 0x00007ff30a50b1a0 0x0 + 140681826840992examples $ wc -c spotify_appkey.key
574 spotify_appkey.keyHm, your application key is almost two times larger than mine (321B). I'm a bit at loss.
Would you be willing to share your application key with me? I'd like to perform some experiments, to see if I can figure out the cause.
Some info about the application key: you generally want to keep your application key secret. Spotify gates access to their API based on the application key, and it allows them to ban an application from using their API instead of banning a specific account.
I cannot acces or read any information from your personal Spotify account using your API key.
I do promise I won't use your application key for anything other than to try and figure out what is wrong, but I understand if you might be reluctant to share it with me. If you are willing to share it with me, you can send the instructions on how to retrieve it to my personal e-mail address: kim@burgestrand.se
pushups
commented
9 years ago Good tip! I downloaded a new app key from Spotify and it started to work. Super strange. Closing this issue.
examples $ wc -c spotify_appkey.key
321 spotify_appkey.keyYay! Great! Glad it solved itself. :)
I'm not sure if this is a libspotify bug or a spotify gem bug.
Preconditions: Mac OS X 10.9.5 ruby 2.1.5p273 - installed under rvm.
Steps:
Result: A seg fault happens.
Crash report: