mirror of
https://github.com/devgianlu/go-librespot.git
synced 2026-04-26 05:15:49 +03:00
[GH-ISSUE #228] "No primary stream" error #147
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#147
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 @2opremio on GitHub (Oct 14, 2025).
Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/228
I have been having this error recently:
failed handling dealer request" error="no primary streamI am at
fc55ed0d21@kernitus commented on GitHub (Oct 17, 2025):
I am also getting a failed handling dealer request, but as a no supported formats. This happens with any track. On commit
f4e53554b6. Might be related to #189@2opremio commented on GitHub (Oct 21, 2025):
I got a slightly different variant of this today:
@devgianlu should I create a separate ticket?
Lately go-librespot has been unusable because of these types of erros :(
Can't go-librespot retry obtaining the stream?
BTW, this all happens through playback transfer requests using github.com/zmb3/spotify, which used to work just fine (in case it helps). Now it tends to fail with golibrespot has been inactive for a while.
@devgianlu commented on GitHub (Oct 23, 2025):
@kernitus This is another kind of issue, to some extent worrying, can you open a new issue so that we can discuss it there?
Yes, this is a different problem, please open a separate issue.
@2opremio commented on GitHub (Oct 27, 2025):
Done: https://github.com/devgianlu/go-librespot/issues/238
@devgianlu commented on GitHub (Nov 4, 2025):
A bit unexpected, can you reproduce the issue by raising the log level to
debug(ortraceeven)?@2opremio commented on GitHub (Nov 4, 2025):
It hasn't happened in a while, I will post when it happens again
@devgianlu commented on GitHub (Jan 29, 2026):
Feel free to reopen if this happens again.