Help Wizard

Step 1

NEXT STEP

Notifications won't go away

Solved!

Notifications won't go away

Since the most recent update my Spotify has told me I have notifications. When I try to load the notifications it just shows a loading circle that never goes away. I tried restarting, but every time I restart it just says I have one more notification than I did before. It's really annoying, aesthetically. 

Screen Shot 2015-03-30 at 5.49.33 PM.png
Reply

Accepted Solutions
Marked as solution

Have you tried logging out of the Spotify app, and then logging back in?

MattSudaSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

View solution in original post

9 Replies
Marked as solution

Have you tried logging out of the Spotify app, and then logging back in?

MattSudaSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

Having same problem. And no way to disable notifications in Preferences.

Logging out did work, thanks. But that isn't a I want to do every day.

What a terrible 'upgrade' this has been.  I'm seriously thinking about switching to Rdio.

Should have thought of that. Thanks!


 

I have tried logging in and out, it just gets rid of the current notifications, but the problem still persists after I receive any new messages, the notification still sticks until I log in and out again. Any help would be amazing!

Has anything happened with this?

 

I have the same issue and it's really annoying. I have a friend's message with a song in it from over a year ago and I just want the notification to go away

Nope, still an issue for me!

I've had the same notification pretending to be new for over a year now.

 

Really annoying.

Logging out is not a solution. It is a work around for a problem that Spotify has not fixed. I and others would like to see this fixed by Spotify.

This is not a solution, it's a workaround. This issue is not solved.

Suggested posts