[GH-ISSUE #743] Spotify player using the wrong client id when going to authenticated #1376

New issue

Closed

opened 2026-03-14 14:34:41 +03:00 by kerem · 4 comments

kerem commented

2026-03-14 14:34:41 +03:00

Owner

Originally created by @ascaletty on GitHub (Jun 5, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/743

Spotify-player uses the default client id in the url even when i change it in app.toml or use client_id_command instead. i get an illegal scope every time i try to authenticate as a result. I have made an app on spotify dashboard and specified the id in the app.toml but it seems to still be broken.
version 0.20.5
arch linux

Originally created by @ascaletty on GitHub (Jun 5, 2025). Original GitHub issue: https://github.com/aome510/spotify-player/issues/743 Spotify-player uses the default client id in the url even when i change it in app.toml or use client_id_command instead. i get an illegal scope every time i try to authenticate as a result. I have made an app on spotify dashboard and specified the id in the app.toml but it seems to still be broken. version 0.20.5 arch linux

kerem

2026-03-14 14:34:41 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-14 14:34:57 +03:00

Author

Owner

@pbizimis commented on GitHub (Jun 12, 2025):

Same for me. Were you able to fix it?

@pbizimis commented on GitHub (Jun 12, 2025): Same for me. Were you able to fix it?

kerem commented

2026-03-14 14:35:03 +03:00

Author

Owner

@ascaletty commented on GitHub (Jun 14, 2025):

no i was not able to fix it
On Thu, Jun 12, 2025 at 12:31:10PM -0700, pbizimis wrote:

pbizimis left a comment (aome510/spotify-player#743)

Same for me. Were you able to fix it?

--
Reply to this email directly or view it on GitHub:
https://github.com/aome510/spotify-player/issues/743#issuecomment-2967939578
You are receiving this because you authored the thread.

Message ID: @.***>

@ascaletty commented on GitHub (Jun 14, 2025): no i was not able to fix it On Thu, Jun 12, 2025 at 12:31:10PM -0700, pbizimis wrote: >pbizimis left a comment (aome510/spotify-player#743) > >Same for me. Were you able to fix it? > >-- >Reply to this email directly or view it on GitHub: >https://github.com/aome510/spotify-player/issues/743#issuecomment-2967939578 >You are receiving this because you authored the thread. > >Message ID: ***@***.***>

kerem commented

2026-03-14 14:35:08 +03:00

Author

Owner

@aome510 commented on GitHub (Jun 22, 2025):

Spotify-player uses the default client id in the url even when i change it in app.toml or use client_id_command instead.

This is expected. The configured client_id is only meant for Spotify Connect feature and the app will use the default client ID for all other features. I don't know why you failed to authenticate with illegal scope though. Do you have premium Spotify account?

@aome510 commented on GitHub (Jun 22, 2025): > Spotify-player uses the default client id in the url even when i change it in app.toml or use client_id_command instead. This is expected. The configured `client_id` is only meant for [Spotify Connect feature](https://github.com/aome510/spotify-player?tab=readme-ov-file#spotify-connect) and the app will use the default client ID for all other features. I don't know why you failed to authenticate with illegal scope though. Do you have **premium** Spotify account?

kerem commented

2026-03-14 14:35:13 +03:00

Author

Owner

@ascaletty commented on GitHub (Jun 22, 2025):

Yeah I have premium .
On Sun, Jun 22, 2025 at 2:30 PM Thang Pham @.***> wrote:

aome510 left a comment (aome510/spotify-player#743)
https://github.com/aome510/spotify-player/issues/743#issuecomment-2994394349

Spotify-player uses the default client id in the url even when i change it
in app.toml or use client_id_command instead.

This is expected. The configured client_id is only meant for Spotify
Connect feature
https://github.com/aome510/spotify-player?tab=readme-ov-file#spotify-connect.
I don't know why you failed to authenticate with illegal scope though. Do
you have premium Spotify account?

—
Reply to this email directly, view it on GitHub
https://github.com/aome510/spotify-player/issues/743#issuecomment-2994394349,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCR65PGFPSIA67WP6QE2OLT3E3743AVCNFSM6AAAAAB6VXBWB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOJUGM4TIMZUHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@ascaletty commented on GitHub (Jun 22, 2025): Yeah I have premium . On Sun, Jun 22, 2025 at 2:30 PM Thang Pham ***@***.***> wrote: > *aome510* left a comment (aome510/spotify-player#743) > <https://github.com/aome510/spotify-player/issues/743#issuecomment-2994394349> > > Spotify-player uses the default client id in the url even when i change it > in app.toml or use client_id_command instead. > > This is expected. The configured client_id is only meant for Spotify > Connect feature > <https://github.com/aome510/spotify-player?tab=readme-ov-file#spotify-connect>. > I don't know why you failed to authenticate with illegal scope though. Do > you have *premium* Spotify account? > > — > Reply to this email directly, view it on GitHub > <https://github.com/aome510/spotify-player/issues/743#issuecomment-2994394349>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BCR65PGFPSIA67WP6QE2OLT3E3743AVCNFSM6AAAAAB6VXBWB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOJUGM4TIMZUHE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >