-
Notifications
You must be signed in to change notification settings - Fork 79
Spotify api error 404: no active device found. How to fix? #1325
Comments
This has been the behavior of the playback APIs for as long as they've been around. It's really infuriating, and would be nice to see it remedied. |
Is there any sort of workaround to wake the device via the API? Using the desktop client or mobile app first works but entirely defeats the point of these API calls. |
Can you try this , deviceID Can Be Active Or Not Active . |
I have the same issue. My windows 10 PC is not detected and the API returns an empty list ;( |
I was having the same issue and a workaround this issue is sending the device id with the play request URL. The problem is when sending request to the API it does not find any active device and hence the error, which is bad because if a device is asking a call then it is active and the API should understand that. |
Issue found on August 1st 2019.
Endpoint(s):
PUT https://api.spotify.com/v1/me/player/play
Scope(s):
Steps to reproduce:
Expected behaviour:
For the device to always be Active.
Actual behaviour:
Inconsistent 404 error.
Body of post:
I have been using the Spotify api and have been receiving this '404 no Active device' error quite a bit. If I play a song on Spotify and pause it after receiving the error, the error goes away and I am able to send the PUT request to PLAY a song on Spotify from my app.
However if the device has been left without playing a track on Spotify then I receive the same error.
How long after using Spotify to play a track does it take until Spotify api deems the Spotify account/device as inactive? Is there a way to set devices as always being active so I don't have this problem?
The text was updated successfully, but these errors were encountered: