search

hrkfdn / ncspot

Cross-platform ncurses Spotify client written in Rust, inspired by ncmpc and the likes.
BSD 2-Clause "Simplified" License
4.93k stars 206 forks source link

Bad credentials #1504

Closed BrainReader closed 3 weeks ago

BrainReader commented 3 weeks ago

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Install
  2. Try to sign in
  3. Sign in fails and it displays bad credentials

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.

BrainReader commented 3 weeks ago

Update, the Windows version is displaying the Bad credentials error on launching from both powershell and cmd,

joelsleeba commented 3 weeks ago

I have the same issue in archlinux using the family plan as referred in #1500

BrainReader commented 3 weeks ago

The workaround where I copied a working version of ncspot no longer works. I cannot log into ncspot on my laptop or phone.

rosorio commented 3 weeks ago

This seems to be a general issue affecting many spotify OSS clients

https://github.com/librespot-org/librespot/issues/1308 https://github.com/librespot-org/librespot-java/issues/921 https://github.com/kokarare1212/librespot-python/issues/277 https://github.com/Spotifyd/spotifyd/issues/1293

dabalroman commented 3 weeks ago

Spotify disabled the ability to login in to their API using login and password. All devices based on that API utility will no longer work, we are left with zeroconf (discovery).

Check out https://github.com/Spotifyd/spotifyd/issues/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.

hrkfdn commented 3 weeks ago

Duplicate of #1500