mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 09:25:49 +03:00
[GH-ISSUE #615] Player not starting... #1296
Labels
No labels
bug
documentation
enhancement
good first issue
help wanted
pull-request
question
third-party
third-party
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-player#1296
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 @gand0rf on GitHub (Nov 26, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/615
So, long story short. Upgraded system, moved files over to nvme, and have been working on getting things set back up. Got spotify_player working again a couple of days ago. Get a message from Spotify this morning that they noticed "sus" activity and changed my password for me. Got my password updated. Now spotify player will not start even after re-registering with my account.
Error:
I have been working on trying to figure this out. going so far as to create a new app on spotify to get a new client ID.
I also tried using the ID form the docs, but nothing. Looked around for a bit but didn't find anything that helped.
OS: Xubuntu 24.04
Version: 0.20.1
@aome510 commented on GitHub (Nov 27, 2024):
try to re-authenticate the application with
spotify_player authenticateor delete the cachedcredentials.jsonin~/.cache/spotify_playerthen re-run the app@evolutionxbox commented on GitHub (Nov 29, 2024):
I've done this and I still see there error. I also do not have a
~/.cache/spotify_playerfolder.OS: macOS Sonoma 14.6.1
Version: 0.20.1
@gand0rf commented on GitHub (Nov 29, 2024):
@aome510 Just wanted to touch base. I haven't had a chance to try this out myself. Been traveling for work this week. But I installed player in my worklaptops wsl term, and it loads just fine. Except for there is no spotify deamom for it to connect to, but I was just testing the launching and connecting it to my account. Should get back home tonight to see if this works for me.
@aome510 commented on GitHub (Nov 29, 2024):
that's weird. What is the result of
spotify_player --help?@gand0rf commented on GitHub (Nov 30, 2024):
@aome510 That fixed it!! Thank you. Done on my end. Not sure if you want to leave this open for evolutionxobx's issue or not.
@aome510 commented on GitHub (Nov 30, 2024):
I think it might be something unrelated. Will close this for now
@evolutionxbox commented on GitHub (Dec 3, 2024):
@aome510 I'll create a new ticket if I can, because no matter how many times I runspotify_player authenticate(and follow the link) nocredentials.jsonis created.Sorry @aome510, I hadn't started the Spotify daemon either. Thanks @gand0rf 👍