There are many reasons why this can be hapenning to you.
A few things you can try to do to fix it are:
- Ensuring you setup your app exactly according to the tutorial
- Waiting a few seconds until the opened authentication page is fully loaded
- Trying different localhost ports for the redirect uri
- For example: using
http://localhost:1234/callback
instead ofhttp://localhost:8888/callback
- Don't forget to update your
settings.ini
file accordingly by replacing theredirect_uri
field with the new uri!
- For example: using
- Deleting the
.cache
file if it's present and trying again - Authenticating using a client secret
- To do this, you need to go to the same page where you got your client id from, copy the client secret and add it to the
settings.ini
file in front ofclient_secret =
- You also need the client id you already added for it to work (you don't need to change it if you already set it up)
- To do this, you need to go to the same page where you got your client id from, copy the client secret and add it to the
Caution
Unlike your client id, your client secret is very sensitive information. As such you have to be very careful not to share it anywhere, and only use it after trying the other options.
If all those fail, feel free to open an issue or contact me through my discord!
Because apps that replace native Spotify functionality are against Spotify's developer terms of service, I am unable to register a client id that could be shared across all users of this app.
Because of this, each user has to supply their own client id to connect to the Spotify web api.
You can find how to get your client id here.
Some antivirus programs might wrongly flag this app as a virus.
This is simply because the app is not signed, as doing so can cost upwards of 359$/year, and I am both unable and unwilling to pay that amount for a small passion project.
Still, if you're suspicious you can look at the source code for the app in this repository and run it directly, or compile an exe yourself.