[GH-ISSUE #176] Latest spotify android client (v8.4.42.722) does not detect librespot #118

Closed
opened 2026-02-27 19:28:56 +03:00 by kerem · 8 comments
Owner

Originally created by @romqu on GitHub (Mar 1, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/176

Hello everybody,

first off all, thank you for the great project, I really appreciate the work you're doing.

I recently updated the android client to the newest version and since then it has stopped to list librespot
as an available device. It does work with the previous one (v8.4.39.673) though.
I'm using a Galaxy S6 (LineageOS 14.1) and librespot (build from master today) is running on a raspberry pi 3 with the latest moode os.
Maybe the issue is on my end, but I haven't changed anything in my setup line besides upgrading to the latest librespot version.

I apologize in advance if I have missed something.

Originally created by @romqu on GitHub (Mar 1, 2018). Original GitHub issue: https://github.com/librespot-org/librespot/issues/176 Hello everybody, first off all, thank you for the great project, I really appreciate the work you're doing. I recently updated the android client to the newest version and since then it has stopped to list librespot as an available device. It does work with the previous one (v8.4.39.673) though. I'm using a Galaxy S6 (LineageOS 14.1) and librespot (build from master today) is running on a raspberry pi 3 with the latest moode os. Maybe the issue is on my end, but I haven't changed anything in my setup line besides upgrading to the latest librespot version. I apologize in advance if I have missed something.
kerem closed this issue 2026-02-27 19:28:57 +03:00
Author
Owner

@awiouy commented on GitHub (Mar 2, 2018):

This should be fixed by #167
Do you have a log?

<!-- gh-comment-id:369901661 --> @awiouy commented on GitHub (Mar 2, 2018): This should be fixed by #167 Do you have a log?
Author
Owner

@romqu commented on GitHub (Mar 3, 2018):

Hello,

thank you for the reply.

Do you have a log?

I suppose you mean a log from the spotify application?
I already took a look at the logcat but couldn't find anything useful.
But I can of course provide one.

In the case of a librespot log, I executed the following command.
RUST_BACKTRACE=1 librespot --name name --backend alsa --verbose

Due to the fact that it doesn't show up in the application, there is no other output than:
INFO:librespot: librespot 8f8eb8c (2018-02-28). Built on 2018-02-28. Build ID: FL46vJJ7 DEBUG:librespot_connect::discovery: Zeroconf server listening on 0.0.0.0:0

But I get the feeling the issue is on my end, since I seem to be the only one that does experience the problem.
I will just keep an eye on it and do some further testing.

<!-- gh-comment-id:370132678 --> @romqu commented on GitHub (Mar 3, 2018): Hello, thank you for the reply. > Do you have a log? I suppose you mean a log from the spotify application? I already took a look at the logcat but couldn't find anything useful. But I can of course provide one. In the case of a librespot log, I executed the following command. ` RUST_BACKTRACE=1 librespot --name name --backend alsa --verbose` Due to the fact that it doesn't show up in the application, there is no other output than: `INFO:librespot: librespot 8f8eb8c (2018-02-28). Built on 2018-02-28. Build ID: FL46vJJ7 DEBUG:librespot_connect::discovery: Zeroconf server listening on 0.0.0.0:0` But I get the feeling the issue is on my end, since I seem to be the only one that does experience the problem. I will just keep an eye on it and do some further testing.
Author
Owner

@ghost commented on GitHub (Mar 3, 2018):

My Spotify updated yesterday too. The device shows up in the devices tab, but as soon as I choose it, it crashes.
thread 'main' panicked at 'calledResult::unwrap()on anErrvalue: WireError(InvalidEnumValue(13))', /checkout/src/libcore/result.rs:860:4 note: Run withRUST_BACKTRACE=1for a backtrace. DEBUG:librespot::spirc: drop Spirc[0] DEBUG:librespot::player: drop Player[0] DEBUG:librespot_core::session: drop Session[0] DEBUG:librespot_core::mercury: drop MercuryManager DEBUG:librespot_core::session: drop Dispatch

<!-- gh-comment-id:370143447 --> @ghost commented on GitHub (Mar 3, 2018): My Spotify updated yesterday too. The device shows up in the devices tab, but as soon as I choose it, it crashes. ` thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: WireError(InvalidEnumValue(13))', /checkout/src/libcore/result.rs:860:4 note: Run with `RUST_BACKTRACE=1` for a backtrace. DEBUG:librespot::spirc: drop Spirc[0] DEBUG:librespot::player: drop Player[0] DEBUG:librespot_core::session: drop Session[0] DEBUG:librespot_core::mercury: drop MercuryManager DEBUG:librespot_core::session: drop Dispatch `
Author
Owner

@sashahilton00 commented on GitHub (Mar 3, 2018):

@aopst that issue was resolved in #167. Rebuild librespot with the latest commit and it'll work again.
@romqu I'm inclined to agree that the issue is likely on your end. To test this, could you start librespot with -u YOUR_USERNAME added, and login manually. If the device then shows up and you are able to play music to it from the spotify app, then that isolates the problem to your network at least.

<!-- gh-comment-id:370148349 --> @sashahilton00 commented on GitHub (Mar 3, 2018): @aopst that issue was resolved in #167. Rebuild librespot with the latest commit and it'll work again. @romqu I'm inclined to agree that the issue is likely on your end. To test this, could you start librespot with ```-u YOUR_USERNAME``` added, and login manually. If the device then shows up and you are able to play music to it from the spotify app, then that isolates the problem to your network at least.
Author
Owner

@romqu commented on GitHub (Mar 3, 2018):

@sashahilton00
Indeed, it works with the username and password supplied. But discovery mode does not work. Only with the previous android version. Really weird.
Anyway, I apologize for the inconvenience.

<!-- gh-comment-id:370165482 --> @romqu commented on GitHub (Mar 3, 2018): @sashahilton00 Indeed, it works with the username and password supplied. But discovery mode does not work. Only with the previous android version. Really weird. Anyway, I apologize for the inconvenience.
Author
Owner

@jollybully commented on GitHub (Apr 18, 2018):

@romqu - I'm having the same problem when using the Spotty fork of librespot and am at my wits end, I'm beginning to think it's a network issue on my end and would be interested to know if you ever found a solution?

<!-- gh-comment-id:382560991 --> @jollybully commented on GitHub (Apr 18, 2018): @romqu - I'm having the same problem when using the Spotty fork of librespot and am at my wits end, I'm beginning to think it's a network issue on my end and would be interested to know if you ever found a solution?
Author
Owner

@michaelherger commented on GitHub (Apr 19, 2018):

@jollybully - some users mentioned they had to to wipe the Spotify app's data/cache. And make sure you enable local discovery or disable local only discovery in the app.

Did you get in touch with me on forums.slimdevices.com?

<!-- gh-comment-id:382615834 --> @michaelherger commented on GitHub (Apr 19, 2018): @jollybully - some users mentioned they had to to wipe the Spotify app's data/cache. And make sure you enable local discovery or disable local only discovery in the app. Did you get in touch with me on forums.slimdevices.com?
Author
Owner

@DarkNinja77 commented on GitHub (Sep 16, 2019):

I have the same problem for about a year and still have it. Librespot doesnt show up as a device to play to.

<!-- gh-comment-id:531965951 --> @DarkNinja77 commented on GitHub (Sep 16, 2019): I have the same problem for about a year and still have it. Librespot doesnt show up as a device to play to.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/librespot#118
No description provided.