-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
An error has occurred when searching, then is fine, then not again #1728
Comments
I am having the same issue on the same OS, Version 0.6.40. I've never been able to play a song. |
I'm going to paste what I said in another thread: Can you try the following:
Also you can open the developer tools, check the network tab, and see why it's failing. |
OS X ARM64 / Nuclear 0.6.40 |
Same problems here on M1 pro MBP.
In developer tools, there are loads of repeatedly errors.
However, if open the app via cli,
|
Ive attached the log, but as mentioned above by @pomelo its the same couple errors looping until Nuclear crashes or I force-quit. This is from clicking a song from the Listening History that just worked literally 15-minutes ago. I tried this with the first 10 songs in the Listening History and all had this exact error (except the searched for song of course :)
and then a lot more repeating until crash. The full log is attached. |
Yeah we know. Any program that loads streams from Youtube is currently broken. Gotta wait for a fix. |
Platform:
OS X ARM64
Nuclear version:
0.6.39
Description of the issue:
After playing for a while (exact amount of time varies) every track simply displays "An error has occurred when searching". Even tracks that previously played fine now get this.
After restarting Nuclear the problem with the exact same track(s) disappear and they play fine
But the problem re-appears sometimes several times per day.
This seems related to #1641 but I don't get the exact same error message so feel free to link the two if it looks to be the same.
Didn't open developer tools, but happy to do so next time the problem shows up if that's helpful
Also thanks so much for the great player!
The text was updated successfully, but these errors were encountered: