Interesting bug on iPhone lockscreen

[tq]

Hello everyone,

I've recently updated to Spotify 0.5.2 and noticed that the iPhone Spotify app is causing an issue on the iPhone lockscreen in regards to displaying the currently playing track name. When I begin to play the first song of an album, it plays correctly. If I then try to skip to the second track through the lockscreen, it also works correctly and the song name under the clock is updated correctly. However if I try to skip again to the third track, the third track begins to play but the second track's name still displays under the clock. I can skip forward and back at will from the lockscreen, but the second track's name will always be displayed. I thought this was iOS6's fault, but then I tested it on an iPod Touch 4G running 5.1.1 and got the same issue, which leads me to believe it was a Spotify bug. I then used iTunes to revert back to 0.5.1 on my iPhone running iOS6 and the issue has gone, further underlining the fact that (for me at least) it has been a bug introduced in 0.5.2. Can anyone replicate this bug? I'd like to see if a patch could be issued so I can get the new Radio feature without losing the ability to see my song name in the lockscreen.

[stealth210]

I agree with bmj1086. I moved to Mog and haven't looked back. I am unsubscribing from this thread as well. It's just sad and I don't want to read any more about this issue.

[domsbombz]

I've switched to MOG, too. It's just a simpler app. Can't sync my own music, but I can just use the Music app for what I own anyway. 

[zefloflo]

This is unbelievable. Users start to exchange advices about Spotify's competitors, but the dev team doesn't even bother to answer.

I can't wait to switch to another service myself - don't want to give any more money to such disrespectful people.

[Richard]

---

@zefloflo wrote:

This is unbelievable. Users start to exchange advices about Spotify's competitors, but the dev team doesn't even bother to answer.

I can't wait to switch to another service myself - don't want to give any more money to such disrespectful people.

---

The developers don't tend to post directly on our Community. They're usually busy developing, you see. They do post occassionally though, and do actively read these threads for bugs/feedback.

On this issue, I can assure you that it hasn't been forgotten about. We don't have an update for you at this time, but we will let you know as soon as there's more to say.

[benexclaimed]

Pretty hilarious that after months and months of silence, the response is only to nitpick a user's choice in language (for saying 'dev team' instead of 'customer service team'). Great job.

[zefloflo]

Alright then - still no useful information about the problem, but I get free sarcasm.

With such a great service, it's a pity that you insist on losing customers for a small (but annoying) technical glitch and/or a lack of professionalism in your tech support.

But it's your choice. All I can say is : goodbye Spotify (and that includes the dev team, the tech support team, and whatever...)

[richmondn]

Well, that wasn't an efficient response Richard. I've left and went to MOG which I kinda enjoy but this bug annoyed the hell out of me. And this happened several months ago and you've had 2-3 updates since then. And lastly, thank you Richard for your hostile response. It cleared up everything I needed to know (sarcasm)

[Richard]

Apologies for how my response came across, I just wanted to clear up the distinction between us community folk and the Spotify developers. Sometimes people get mixed up between the two.

And we will let you know just as soon as there's more news on this - I'd like to see this fixed just as much as you (I'm on your side!)

No hard feelings?

[AndyRiley]

Can I add my voice to those seeking this bug to be resolved?

The bug has been present and known about for upwards of six months now, we have advised on several occasions that it is being worked on, but no resolution as yet.

It is a most annoying bug and detracting from my Spotify experience.

Thank-you

Andy

[darren_85]

I too am sick of this bug

I only listen to spotify over Bluetooth in my car and not knowing the track name correctly is very frustrating. If I want to recommend a track to somebody, I can't because I don't know the trackname!


I really must give napster a try when my sub ends on 27th jan.

[tehmark]

Just wanted to post and say that I just cancelled my Spotify subscription because of lack of support.  I've used Spotify since 2010.  I'm switching to Rdio because I can't wait around for a year to have a simple problem fixed.  Thanks for nothing.

[danc27]

One can only hope the next version of the iOS app gets rid of the ton of bugs that currently exist, including this one.  It really has been ever since the iPad (universal app) was released.

[Whintersby · Accepted solution]

The only solution I have found to this issue is one that was briefly mentioned earlier in this thread.

Search for and install "Spotify for IOS4".

This version does not include this very irritating defect, although iPhone5 users will have to deal with the app not consuming the full screen - something I'm willing to put up with.

[WhatisIX9]

Same bug here. Pathetic Spotify - FIX IT!

iOS 6.1

iPhone5

Latest Spotify @ 13Feb

[itsB · Accepted solution]

Also left Spotify for MOG.  Same selection, price, quality on much better software platform.  Thanks to previous posters for pointing us to MOG.  Bye

[danc27]

New version of Spotify iOS app today and guess what, still not fixed.

Pretty ridiculous.

[ceevee]

New iOS app version 0.5.10.14 today. Bug of wrong song name on lock screen still exists.

[benexclaimed]

Hilarious.

[yoitsmike92]

if this isn't fixed in the next update I will be canceling my subscription as well, and moving to rdio most likely

[wjhunt]

Spotify should be bloody ashamed of themselves for not fixing this annoying bug and making the iPhone app worse instead of better. There's no real alternative for me here in the Netherlands which offers seamless integration with my own mp3s like Spotify does, but as soon as it's there, I'm gone if this isn't solved.