Joann Mõndresku

Try shutting down Spotify, wait for around ~15 seconds and try relaunching it. It seems as your Spotify launched on another port possibly due to quick close and open.

I recall you having Spotify 0.9, that might be the culprit.

@samonyt that's not a "fix" to the root of problem, though.

async isn't supported in older versions of node, please update your node version.

Hello, have you by any chance blocked `open.spotify.com` via your hosts file. Can you even go there with your browser. If you are using custom DNS servers, please change them...

This is now resolved after the latest PR. Enjoy!

I think I found the potential culprit. It seems like the current code checks if the uri is different, rather than checking if it's been repeated or not.

Did you [try reading this part of the readme?](https://github.com/nations/spoticord#stdout-maxbuffer-exceeded-or-some-xmlcsv-parse-error)

Duplicate of #63, and answer remains same. This is a discord-rpc module issue, not Spoticord's, please check their [repository here.](https://github.com/devsnek/discord-rpc)

You left out the error itself. I don't think it's possible to do anything about it though other than creating a fallback saying "you're hiding your activity".