-
-
Notifications
You must be signed in to change notification settings - Fork 218
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
Bad credentials #1504
Comments
Update, the Windows version is displaying the Bad credentials error on launching from both powershell and cmd, |
I have the same issue in archlinux using the family plan as referred in #1500 |
The workaround where I copied a working version of ncspot no longer works. I cannot log into ncspot on my laptop or phone. |
This seems to be a general issue affecting many spotify OSS clients librespot-org/librespot#1308 |
Spotify disabled the ability to login in to their API using login and password. Check out Spotifyd/spotifyd#1293, the author of spotifyd created a small app that enables creating credentials when default zeroconf fails. Unfortunately, there is no way to tell how long the credentials created via zeroconf will last in practice. |
Duplicate of #1500 |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It is supposed to not fail and log me in
System (please complete the following information):
Additional context
I am able to log in to the web version of Spotify
The app is running fine on my laptop running OpenSUSE Tumbleweed (installed through the GNOME Terminal using flatpak). It is also running fine on my phone (installed through Termux running unofficial Lineage GSI). I decided to copy the files from ~/.var/app from my laptop to my PC running Fedora 40 and it skipped the login screen and it went straight to my library.
I was switching from EndeavourOS to Fedora so I had to install the app again. It was working fine on EndeavourOS. I have it installed on Windows 10, but I haven't used it in a while.
The text was updated successfully, but these errors were encountered: