mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 09:25:49 +03:00
[GH-ISSUE #201] spotify_player asking for a username and password #1040
Labels
No labels
bug
documentation
enhancement
good first issue
help wanted
pull-request
question
third-party
third-party
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-player#1040
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mariano-daniel on GitHub (May 22, 2023).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/201
I looked up the main page and documentation page and nowhere this is mentioned.
I tried the API client_id, my email username, the username that shows on my profile, none of them work.
What am I supposed to enter when it's asking for my username? 🤷🏻♂️
@aome510 commented on GitHub (May 22, 2023):
I'm not sure if you have the same thing but in my case, Spotify username should be able to find on the Account Overview website. Here is mine for reference (
usernameis the first one andemailis the second one):@mariano-daniel commented on GitHub (May 22, 2023):
Hello Thang Pham! Yep, that’s the one I’ve used and it did not work. Did it
work for you?
Regards ,
On Mon, 22 May 2023 at 15:29 Thang Pham @.***> wrote:
@aome510 commented on GitHub (May 22, 2023):
Just tried and it still works for me. Can you also provide the logs in ~/.cache/spotify_player` if any?
@mariano-daniel commented on GitHub (May 23, 2023):
spotify-player-23-05-22-02-05.log
Hello @aome510 ! Logs attached. unfortunately they don't seem to be very verbose, just say bad credentials. But i'm entering the same info when I'm login into my spotify profile, but using the username you mentioned on your screenshot (but for me, of course)
@aome510 commented on GitHub (May 23, 2023):
hmmm, that's really weird. At this point, I actually don't know the cause. Can you double check if the same combination of
usernameandpasswordworks in the official Spotify website?@mariano-daniel commented on GitHub (May 23, 2023):
Yep, it works when I login to the site, not when I try the program. I can email you a video with tests.
Thanks!
@adworacz commented on GitHub (May 24, 2023):
I'm running into this as well - I created a new client ID in my spotify account (although I have no idea what to set the redirect URL to, and there's nothing mentioned in the
config.mddocumentation about what to use), so I just usedhttp://localhost:8080/.I've tried twice now to enter my credentials, and I'm getting timeouts of some kind:
@aome510 commented on GitHub (May 24, 2023):
Can u email me an email if possible?
Did u put
client_id = "http://localhost:8080/"? You don't need a redirect URL forspotify_playerunlikespotify-tui.spotify-playerrelies on username/password to authenticate.client_idis only needed if you want to use https://github.com/aome510/spotify-player#spotify-connect.From
config.mddocument, it's not required to specify your own client ID though.@adworacz commented on GitHub (May 25, 2023):
Spotify requires that you specify a redirect URL when creating the client ID, otherwise it errors:
No I didn't. I put the client ID generated via the Spotify Developer website. And I only tried to generate a client ID after the first attempt at using username/password failed.
The same timeout occurs if I comment out the
client_identry inapp.toml.@aome510 commented on GitHub (May 25, 2023):
@adworacz thanks for the clarification. Can you try running
RUST_LOG=debug spotify_playerand send me a corresponding log?Related issue: https://github.com/librespot-org/librespot/issues/1010. Look like this happens because
librespotcouldn't connect to a specific AP.@adworacz commented on GitHub (May 25, 2023):
I'd wager you're correct on that linked issue.
Here's the pertinent logs I see when using
RUST_LOG=debug@adworacz commented on GitHub (May 25, 2023):
Ahhhh now this is interesting - it seems to be related to my work VPN.
If I'm off VPN, I can login just fine and start playing music. If I'm on VPN, I can't start spotify-player at all, even after having successfully authenticated while off VPN.
This is interesting, since I don't have these issues with
spotify-tui+spotifydwhile on VPN.@aome510 commented on GitHub (May 25, 2023):
I also guess that it's a VPN issue or something related.
I think
spotify_playeruses the same setup asspotifydto create a session so I don't know howspotifydworks butspotify_playerdoes not.@aome510 commented on GitHub (May 25, 2023):
Look like the only difference I can find is that
spotifydspecifies a defaultap_port=443:github.com/Spotifyd/spotifyd@1c149822b1/src/config.rs (L855-L860).Can you try if specifying
ap_port = 443inapp.tomlworks?@adworacz commented on GitHub (May 25, 2023):
Worked like a charm!!
I can login, listen to music, the whole nine yards!
@mariano-daniel commented on GitHub (May 25, 2023):
I didn't quite get this request. What should I put in the email?
@aome510 commented on GitHub (May 26, 2023):
I thought you're going to send an email with the video. FYI, my email: phamducthang1234@gmail.com
@mariano-daniel commented on GitHub (May 28, 2023):
Email sent! Thank you.
@aome510 commented on GitHub (May 28, 2023):
@mariano-daniel thanks for the video. Look like the login is failed because you're not in premium account. A premium account is required to use
spotify_player.@mariano-daniel commented on GitHub (May 28, 2023):
But why would it throw bad credentials though? Shouldn't at least me log me in and then throw an error?
@aome510 commented on GitHub (May 28, 2023):
Exactly =)). It used to throw a better error: https://github.com/aome510/spotify-player/issues/29#issuecomment-966393666
This seems to change because I updated the printing mechanism for error from
debugtonormal.The reason is that the third-party library that
spotify_playerrelies mostly for handling Spotify stuff doesn't support it: https://github.com/librespot-org/librespot/issues/862I'll close this issue for now. Feel free to re-open it if you encounter similar issues.
@yashrajbains commented on GitHub (Aug 14, 2024):
Hey there! Following through this thread as I am encountering the same exact issue. Though my issue isn't resolved after specifying
ap_port = 443inapp.tomlAny ideas?
@sewnie commented on GitHub (Sep 23, 2024):
Why isn't this clarified or documented in the README going over how exactly to use it? Would be nice for it to be painless in spotify-player, whether it be done automatically, written out, or a warning to be shipped to new logins.
@sewnie commented on GitHub (Sep 23, 2024):
You mean a new update, not version. I am on the latest git commit of spotify_player and i still have to do this.
@sewnie commented on GitHub (Sep 23, 2024):
still no docs on how to use this side by side with spotify-player
@nikero41 commented on GitHub (Oct 26, 2024):
I still have the same issue on 2 laptops running mac and linux.
I have the correct
client_idand even tried theap_port = 443put still its not workinghere are the logs:
@sewnie commented on GitHub (Oct 26, 2024):
https://github.com/aome510/spotify-player?tab=readme-ov-file#important-notice