mirror of
https://github.com/spotipy-dev/spotipy.git
synced 2026-04-26 16:15:51 +03:00
[GH-ISSUE #541] 403 error Restriction Violated but I have Premium #327
Labels
No labels
api-bug
bug
dependencies
documentation
duplicate
enhancement
external-ide
headless-mode
implicit-grant-flow
invalid
missing-endpoint
pr-welcome
private-api
pull-request
question
spotipy3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotipy#327
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Esamanoaz on GitHub (Jul 13, 2020).
Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/541
Describe the bug
I am getting the 403 error whenever I try to start playback on a Spotify device. This is usually when the user does not have Premium (I think). I have Premium and have double-checked multiple times. The authorization works fine.
Your code
https://pastebin.com/fha4Rbdh
Expected behavior
Actual behavior
Output
https://pastebin.com/Ejizn084
Environment:
Additional context
My code worked on Windows 10, then after being transferred to my pi it has no longer worked.
I thought it was not authorizing correctly (it wasn't) so I fixed that, but I am still getting this same error.
I think this error might have something to do with the scope I am using, which is:
_scope = 'streaming user-read-playback-state user-modify-playback-state'Please help!
@Esamanoaz commented on GitHub (Jul 17, 2020):
I printed the reason (Spotify's reasons for player errors here: link), but it is
UNKNOWN. I don't know where to go from here.@stephanebruckert commented on GitHub (Aug 29, 2020):
Strange that you get
UNKNOWN.Did you also double-check that you are running the correct user (with premium)? using
sp.me(). Sometimes it can use a pre-existing token and even if you specify a differentusername, it won't open the sign in page again. Also make sure you explicitely request to open the sign in page again, by addingshow_dialog=TruetoSpotifyOAuth.If you still have problems, would be good to get a minimal working example so that we can test this more easily on our side, cheers.
@Esamanoaz commented on GitHub (Sep 12, 2020):
I have done lots of tinkering in the past few months and today I found a solution. I was able to play songs via the
urisparameter, but not thecontext_uriparameter. This means I can create a list of the track uris from the album and play that, but I would still like to use thecontext_uriparameter for the sake of convenience. I haven't tested yet, but I am going to assume that since albums don't work for playback, playlists won't either since they both usecontext_uri. Doing the same for playlists that have 100+ songs and have songs added and removed often will quickly become an annoyance.I am very sure that this issue is on Spotify's end. Do you have any ides on how to submit a bug report or fix this?
@stephanebruckert commented on GitHub (Sep 13, 2020):
https://community.spotify.com/t5/Spotify-for-Developers/bd-p/Spotify_Developer