mirror of
https://github.com/Rigellute/spotify-tui.git
synced 2026-04-26 16:15:55 +03:00
[GH-ISSUE #1070] Worked, but now constant 403 #488
Labels
No labels
bug
enhancement
good first issue
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-tui#488
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 @leobergamo on GitHub (Jan 28, 2023).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1070
Hello,
So I successfully installed spotify-tui yesterday. I used spotifyd as the backend. It worked, after some configuring flawlessly. Now, the following morning; I am receiving constant 403 errors from spotify-tui upon startup. I verified spotifyd still starts and runs as before without error, so my deduction is the fault lays somewhere in spotify-tui.
As a side note, I did notice prior, that when spotifyd is not ran in daemon mode with verbose output on; you could see interaction between it and spotify-tui on the console; now no such interaction occurs.
Could this be some sort of "disconnect" locally between spotify-tui and spotifyd ? I don't know, I am lost; I scoured spotify-tui's, spotifyd's and spotify's developer api forums to no avail.
Please advise...
Regards,
Leo C. Bergamo
P.S.
Great work on the TUI though!
@nim65s commented on GitHub (Jan 28, 2023):
Hi,
Same here. I've been using this for months, and now it's only:
@leobergamo commented on GitHub (Jan 29, 2023):
Hello,
Yeah most likely some sort of API change on Spotify's end. Sadly I we'll have to wait to see if the problem is resolved.
@leberknecht commented on GitHub (Jan 30, 2023):
I had the same, i was able to solve it: in my case i was using a sub-account of my family account for the API access, and the solution was to add the email of the root account in the list of allowed user for the sub account (spotify-developer Dashboard => select your app => "users and access").
I stumbled over this by using
spotipypython packages and testing the API with a minimal snippet from their examples likeand env like
Hope that helps somehow.
@sewnie commented on GitHub (Feb 18, 2023):
or use https://github.com/aome510/spotify-player