mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 01:15:55 +03:00
[GH-ISSUE #301] Spotify-Player only is able to connect once after restart #160
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#160
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 @a-usr on GitHub (Nov 27, 2023).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/301
Describe the bug
As already Described in #296, The player only is able to connect to the web api once per OS restart. If i quit or the player fails to start, it is unable to connect once more unless i reboot. I suspect this is because the player doesn't close its connections properly, however as I dont have any knowledge of the inner workings of your program or am able to understand rust, i cant really tell for sure.
To Reproduce
Expected behavior
Spotify Player Succeeds to connect on every atttempt
Log and backtrace
Most recent Log:
Most recent backtrace:
empty
Console output (Localized to German):
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
Additional context
Used the Github Release Build
@a-usr commented on GitHub (Nov 27, 2023):
Upon fiddling around a bit, the Connection issue seems irrelevant, as moving the credentials.json in spotify-player's .cache, starting it, stopping it by Keyboard Interrupt to cancel the the retrieval of credentials, and then moving the credentials.json back solves the issue for 1 start. however a restart of the player still bring up the same error.
@a-usr commented on GitHub (Nov 27, 2023):
Is there maybe some temporary directory that is read from instead if the credentials.json exists in the cache?
@a-usr commented on GitHub (Nov 27, 2023):
Alright, this issue seems to be fixed in the current version of the player. Please do build a new release. Thank you
Closing this as completed.
@a-usr commented on GitHub (Nov 27, 2023):
I take back what i said, in the current version the error just stays for some reason regardless of what i do (rebooting etc)
@a-usr commented on GitHub (Nov 27, 2023):
ok, i am super confused rn, but it appears that my machine is prevented from connecting to certain ports on any server by my firewall. This doesnt make any sense, however since this is not an issue on your side, I'll close this issue