mirror of
https://github.com/devgianlu/go-librespot.git
synced 2026-04-26 05:15:49 +03:00
[GH-ISSUE #132] go-librespot master - failed creating new session #81
Labels
No labels
bug
enhancement
pull-request
spotify-side
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/go-librespot#81
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 @szygmunt on GitHub (Oct 29, 2024).
Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/132
I would like to test some improvements since last stable v0.1 but can't connect to go-librespot from my android app with error:
ERRO[0025] failed creating new session for xxx from yyy error="failed obtaining client token: invalid status code from clienttoken: 400" INFO[0025] refused zeroconf user xxx from yyyI'm using config which i can connect to v0.1 with no problem.
@devgianlu commented on GitHub (Nov 2, 2024):
I have just tested this but I was not able to reproduce. Are you still affected?
@szygmunt commented on GitHub (Nov 2, 2024):
Yes, i'm still affected. Tried "zeroconf" and "interactive" credentials and result is the same:
error="failed obtaining client token: invalid status code from clienttoken: 400"@devgianlu commented on GitHub (Nov 3, 2024):
I have identified a possible issue and fixed it with
github.com/devgianlu/go-librespot@c77366d2e8. I still cannot reproduce, but I hope this fix does with v0.1.1 (to be released).@szygmunt commented on GitHub (Nov 3, 2024):
For clarify: are you talking about MASTER prebuilt binaries downloaded from github "Actions" section? I have no problem with last v0.1 but prebuilt master bin for armv6_rpi is still affected even after your last update (
c77366d).@devgianlu commented on GitHub (Nov 4, 2024):
Oh, I didn't understand that it was the development builds! Fixed now.