-
-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stuck on Connecting... then player vanishes #231
Comments
If I restart librespot when its stuck, it then works normally. |
I've tested using version 122 and 131 and snapshot. I've just noticed the app was updated for android today and ipad 3 days ago, do you think something could have been broken? |
I suppose you are running the latest commit. Is that correct? |
Yes, I built it from source this morning. |
Should be fixed now. |
Thanks, but It's still happening. |
I've made some other changes to that part of the code, not sure if anything should change. Could you post a new log with the Spotify apps versions? |
I've just built it again from the latest source. It took me a few goes this time to replicate. The log dosent say much (in TRACE mode), on selecting I only get this:
If I try again the app comes up with a popup and asks if I want to continue listening on this player or listen on this tablet, its as if its only partly switched over. This was on my android tablet running the Spotify app version 8.5.57.1164 |
I really can't tell what's happening there. It seems to stop before sending the response or during the connection process. Are you able to create a dump (with VisualVM for example) after you have selected to connect with librespot and it's stuck? |
|
I have a heap dump too, but I dont know how to paste that |
As can be seen in the dump, the thread Are you able to start librespot with username and password? Are the two instances running on the same machine?
The one you sent is fine. |
Yes the instances are on the same machine, I am spawning them from node.js (child_process) each with their own unique api port. I can test with username and password but I dont want to use it that way in the end as its meant for visitors and friends etc.. |
If its waiting from the Spotify server, could it be a wiered internet connection issue? I have multi WAN set up on my router with 4G as my main connection and a slow ADSL connection, I am just trying it with 4G turned off and its not failed yet, I'll keep testing that. |
I've just tried running two instances in two different folders from the command line and it worked fine. Could you try doing it manually? My steps:
A simple test confirmed that it is not the case. |
It's not failed yet since turning off 4G, I'll keep trying..... Sorry for wasting your time, but it was a big help that you pointed out that it was stuck waiting for the Spotify server, to be honest I can't understand those logs. Thank you very much for your help. I'll close the issue after I've tested it for a while. |
All seems good now. |
Not really, because it is just a network issue. I could try and set a timeout for the socket, but that would influence other components across the project. |
When connecting (using Spotify connect) for the first time after a long while or reboot or app restart, I sometimes get into a situation where the Spotify app sticks on connecting... and then if I try again the librespot player has gone from the list.
This has happened many times, I can get it to fail by restarting my tablet (or just the app) and restarting librespot.
I have tried setting log level to trace but theres no significant info output.
Then there is no furthur output.
I have tested it on an iPad, Android tablet and an Android phone.
The text was updated successfully, but these errors were encountered: