Latest version not working at all (Mac OS X)

[djaykay]

Support template from http://community.spotify.com/t5/Help-Desktop-Linux-Mac-and/Mac-Troubleshooting-Spotify/td-p/105281

Description

I was prompted to update Spotify and did so. It completed successfully but after relaunching I cannot play any music, nothing loads, not hte activity sidebar, discover, browse, search. I have done a clean reinstall after deleting the cache and app support directories.

A more detailed description, using numbered steps

1. Loaded up Spotify, can't play any music, search, use discover, nothing. 

What I expected to happen

It would work

What actually happened

It doesn't work

My Operating System

OS X 10.9

My Spotify version

0.9.6.72.ge389c074

My internet provider and country

Fluidata

My username

djaykay

Do you have any screenshots you can attach to more clearly explain your issue?

https://www.dropbox.com/s/sl74p44n9f5lajw/Screenshot%202013-11-19%2010.05.16.png

https://www.dropbox.com/s/qrev1l5mluu7m9z/Screenshot%202013-11-19%2010.11.10.png

https://www.dropbox.com/s/v5y94l2kkqbg43z/Screenshot%202013-11-19%2010.11.24.png

https://www.dropbox.com/s/uihl4ws2hy197xs/Screenshot%202013-11-19%2010.11.38.png

https://www.dropbox.com/s/44f5veucvga633z/Screenshot%202013-11-19%2010.11.46.png

My colleagues are using the same version of Spotify on Mavericks with no issue so I don't believe the internet connection to be at fault. 

Also, some (relevant?) log entries that occur when I click on any part of the interface and it doesn't load anything, are these 2, repeated:

19/11/2013 10:54:23.482 Spotify Helper[46932]: Internals of CFAllocator not known; out-of-memory failures via CFAllocator will not result in termination. http://crbug.com/45650
19/11/2013 10:54:23.980 Spotify Helper[46932]: The function `CGFontSetShouldUseMulticache' is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance.

[Peter__]

Can you try starting Spotify from a terminal using:

/Applications/Spotify.app/Contents/MacOS/Spotify --disable-accelerated-layers --disable-accelerated-fixed-root-background

And see if that a) works (I've only tested on Windows) b) makes any difference?

[djaykay]

Hi Peter,

Thanks for the reply. This hasn't fixed the problem but has produced a log which may help you guys figure out what's up. Log is attached.

Cheers.

[Peter__]

Thanks - I will pass those over to the Spotify team for you. 

[denisesballs]

Seeing this same issue. The Mac app is unusable after the latest update last week. The web player does work. Please let me know if I can assist troubleshooting.

[djaykay]

Until this is fixed, I downloaded the old version from http://mac.filehorse.com/download-spotify/old-versions/

It works, so the issue seems definitely to lie with the latest update.

[denisesballs]

I didn't trust downloading Spotify from another site, so I downloaded this version here - http://download.spotify.com/Spotify-0.8.5.dmg

Which I found in this thread - http://community.spotify.com/t5/Help-Desktop-Linux-Mac-and/Help-my-spotify-doesn-t-open-anymore-on-M...

Of course Spotify will try to keep upgrading itself with no way to disable it, so if you go to /Application in Finder, right-click and go to "Get info" and click "Locked", it will prompt you for a password to upgrade each time you restart it. Then you can simply click cancel, and it won't update.

[SpencerNorman]

I'm also having this exact issue on OSX Maverics on a late 2012 15" Retina Display MBP.

[Peter__]

I have reported and escalated client issues on OS X 10.9 to the Spotify team since there are multiple reports (of different issues) here on the community. 

[djaykay]

Thanks Peter, apprecaite it.

[SpencerNorman]

Thanks Peter. In the meantime reverting back to an older version of spotify has given me the ability to listen to music again, and locking the app from updating via "Get Info" has kept it from updating.

[denisesball]

Just FYI Peter, I am not on OSX 10.9 (Mavericks) yet, but still seeing the same issue.

[tattooedarmo]

I'm also seeing the issue.  I uninstalled and reinstalled hoping that might do the trick, but it's stuck on the discover page.  After searching for an artist in the search tab, the named appears, but after clicking on it I go no where!

I hate paying for premium if this is how it's going to be.

[geoff2k]

I too am seeing this issue.  Is there any update?  Is going back to a previous version from a non-sanctioned site our only solution if we don't want to use the webplayer?

[denisesball]

Just FYI for others, I am no longer having this problem after upgrading to OSX 10.9 Mavericks (free upgrade) and upgrading Spotify.

[denisesball]

Also, I did notice that my version since I upgraded to Mavericks is newer than the one reported in the OP. It's 0.9.6.81.gd359a796.

[djaykay]

FYI I got a new MBP the other week and it's totally fine with the latest Spotify.

I wonder, how many people with this issue had a case-sensitive filesystem? On my previous MBP that had the problem I did. On this new one as I've not reformatted I do not. Just trying to figure out if that has anything to do with it as some apps don't like it at all (e.g. Steam) and need special hacks. Maybe a hardcoded directory was added in the latest release or something?

[geoff2k]

I am unfortunately still seeing the issue under Mavericks [OS X 10.9 (13A3017)] with Spotify client 0.9.6.81.gd359a796.

[dekz]

Also having this issue, reported here.

[geoff2k]

I cancelled my premium subscription over this issue, and while that appears to have given me a bit more priority in my support requests, it still has not solved the issue.  Currently the developers are apparently on Christmas break, and I am awaiting to hear back.  So far they have had me:

1. reinstall from scratch multiple times

2. login as one of their test accounts and see if I still see the issue (I do)

3. "refreshed" my playlists (whatever that means) which is apparently a server-side issue, and that did not fix it either

I'm at a loss for why it is taking this long to resolve this.  My first request for support was to @SpotifyCares on December 8th.