-
Notifications
You must be signed in to change notification settings - Fork 0
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
App won't open #2
Comments
Alright I figured out I needed to remove the <> from around the id, but now it's giving me a different error:
This happens both on the app and on the web player. |
Can you show what's inside your settings.ini file? You can include the client id its not sensitive info but if you don't want to just delete some random characters from it |
Here's my settings.ini file: [theme] [spotify] [lyrics] |
That's weird, I can't replicate this error. |
My mom acrually got a premium duo plan out of nowhere the other day so I don't need the app anymore, don't worry about the workaround. |
I'll add the workaround anyway if anyone has the same issue lol but good for you :) |
Wait did you maybe copy your client secret instead of your client id? |
Also another thing you can try is deleting the |
If none of that works, as of v0.6.0 you can also authenticate the app using your client secret. Caution Your client secret is very sensitive information and you should be very careful with it, so only do this if the other options fail 👍 Also I still haven't been able to replicate the error so I'm not 100% sure this will fix the issue. |
Although the client secret is placed in your settings.ini file, it doesn't work if your localhost is at 8888, so what I did to enable it was to change the redirect URI from http://localhost:8888/callback to like e.g. http://localhost:8080. You still have to manually edit it in the developer page of Spotify and the settings.ini file. What I do think atm is that prolly the localhost:8888 could be used by other services though since I'm running a VM alongside Windows 11 and that apparently happened. Hope this helps a lot! |
Oh I didn't think of that yeah maybe the 8888 port is already used by something else :P |
Describe the bug
I found and set my client ID in the settings.ini file, but when I run the exe this tab opens in my browser (Firefox):
"https://accounts.spotify.com/authorize?client_id=<my client id here, don't know if it's dangerous to share>&response_type=code&redirect_uri=http%3A%2F%2Flocalhost%3A8888%2Fcallback&code_challenge_method=S256&code_challenge=CpfoBs8911s7h-Jbmh-n3P8WXaDe9Wyor1wMJgnVdKA&scope=user-read-currently-playing"
which displays in plain text:
"INVALID_CLIENT: Invalid client".
Nothing else happens.
Expected behavior
The app opens and works as expected.
Real behavior
The app doesn't open.
To Reproduce
List the steps needed to reproduce the bug:
Context/Environment
Write here the information about the environment in which the bug happens, such as:
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I am using Firefox and a cracked Spotify client (BlockTheSpot), but it also doesn't seem to work if I have the web player open.
The text was updated successfully, but these errors were encountered: