Aoede not appearing in Connect to a device

[JakePorter22]

Using the latest prebuilt binary for Windows.

Managed to run it two hours ago with no issues, got it connected to my server and played on Spotify. Trying to run it again now after closing my CMD window and turning off the PC. I get the message that everything is Ready, but no option is showing up in Spotify to connect to the device. Removed all variables in Regedit and set them again with the same issue.

Searched through the Librespot issue tracker, but didn't find much that could help.

I also received emails from Spotify the first three times I ran the exe regarding a new login, but running it now does not yield an email.

Is there a way to fix this or am I better off running the source code?

[codetheweb]

If you set the DEBUG environment variable to * (through the same process as the others) it should log whether or not a Spotify session is being created.

[JakePorter22]

Is there a log file created somewhere? I created the variable as described but I am not seeing anything new in the command window.

[codetheweb]

It will log it to the same terminal session you started it from. If you don't see anything the environment variables probably aren't getting set correctly.

[exproject]

This happens to me as well. Using the pre built binary, the console just logs an invite link (even when using a bot token that is already joined to a server.) Tried setting DEBUG=* in the config file but it didn't result in anything more logging to the console.

[codetheweb]

Sorry, got the env vars mixed up with npm's debug package. I think setting RUST_LOG=debug should log more info.

[exproject]

Hmm, unfortunately no luck still. Still says ready and invite link, but no extra logs to console and still not in Spotify:

Screenshot omits DISCORD_TOKEN as that was done with setx.

I do see the bot sign into discord for a split second when the executable runs though.

EDIT: Worked around this by switching to the docker version. Not sure what is different there, but it is able to play from Docker.

[codetheweb]

I think it probably gets applied too late if you add it to config.toml, try setting it with setx?

[exproject]

This was actually an error on my part and both Docker and executable work. The issue (for me at least) was that the while the bot had server level permissions to connect to voice and play, the voice channels were not inheriting perms from the server. Granting the bot same permissions to the channel made it start working and show Aoede in Spotify. I'm guessing while I was tinkering with Docker I made the permission change but didn't connect the dots at the time. Now that I think about it further, I think I was testing in a channel that is normally hidden to @ everyone so perhaps the bot didn't even see me in that channel.

Maybe nothing to change here, but a note to check the voice channel permissions could be nice as the bot doesn't give any indication that it can't follow the user into that channel and it not showing up in the Spotify device list til it sees you gives the impression that something is broken.