Closed rohit-ganapathy closed 3 years ago
hi @dflemstr @jkp @vzctl
I'm facing this issue with seek as well. Can you please look into this ? This bug is causing major issues with my app.
Thanks, Ishaan
hi @jkp @dflemstr @vzctl, I have been facing the same issue too. It has rendered core features of my app unusable. Could you please have a look at this soon as it is affecting the future releases.
Regards, Hari
Hey guys please look into this... it is still not resolved
Hey @rohit-ganapathy , I have been facing the same issue too. Can you please look into this @jkp @dflemstr @vzctl. Thank you.
Regards, Jaideep
Hey guys can we at least acknowledge that there is an issue? Sorry for being so persistent but it is a question of losing users.
@JDKhare can you confirm which version of Spotify it is?
@dflemstr I'm happy to work on this issue if you can help us identify the core issue
Thanks, Ishaan
@rohit-ganapathy Same as yours. Wonder if it's an issue with the India release? Are you using an Indian account?
Hey I'm facing a similar issue as well. It would be of great help if you could look into this. Thanks
Same issue... Please fix that, this error was fixed a year ago by updating the spotify app but now it returned :-(
Same issue here as well. Does anyone from Spotify actually look at these boards?
Same issue here. My app's core features are unusable until this is fixed. Could you, please, have a look at this soon? It is preventing me from launching the app. Thanks!
A few months ago I read that Spotify prefers to discuss developer problems on this forum, not sure if they are still checking the github issues, woul be nice to know.
But to have a response I guess you should post the problem here: https://community.spotify.com/t5/Spotify-for-Developers/bd-p/Spotify_Developer
@tobika Unfortunately they don't respond there either: https://community.spotify.com/t5/Spotify-for-Developers/getting-Error-quot-message-quot-quot-Cannot-seek-in-song-UNKNOWN/m-p/5026584
ups, sorry @jknightco didn't see it there, thanks for the link
To clarify: I guess the problem is that we seek right after the result callback of the play command? If I seek once the song is already playing everything works quite well.
Did someone find a way to determine from which moment it is safe to seek? Best way for sure would be the spotify app getting back to it's working state like it was before.
found one hack. Use onPlayerStateChange event listener to know when the context has truly shifted to the uri and only then seek. I've realised that spotify player context does not shift immediately after the call to playUri resolves successfully.
I'm going to need more precise steps to reproduce. I can't see any issue with the sample app and seek.
After updating the app, I get the following error when I try to seek to a position in a song: Suddenly getting this error : [Error: {"message":"Cannot seek in song: [UNKNOWN]"}]
Issue found on 30th Aug 2020.
Spotify App Version:
8.5.73.824
SDK Version:
0.70
OS Version:
Android 9
Scope(s):
App Remote
Steps to reproduce:
Expected behaviour:
Should seek song to given position after playing
Actual behaviour:
Throwing error : [Error: {"message":"Cannot seek in song: [UNKNOWN]"}]