You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
today I stumbled over this project and gave it a try:
when I start it, my Chrome browser opens up the page to authorize Spotify.ahk. I confirm this, but then the page loads forever and Spotify doesn't show up in the browser tab. I guess that's not normal, am I right?
Second, in my user account I can see that Spotify.ahk was successfully registered as an allowed application.
But if I open Spotify web player in Chrome manually, the shortcuts still don't work.
Is this project still working for someone? Or is it outdated?
Thanks
The text was updated successfully, but these errors were encountered:
As far as I can tell, there's nothing wrong with the authorization flow. I was able to get a token in both Chrome and Firefox.
People have been running into this kind of problem for a while now, and I've never been able to reproduce it between various different computers and browsers and networks, so I really don't know.
I am using a crappy socket library and a crappy HTTP library for auth, but I don't want to blindly blame them. I don't suppose you happen to be running some other software which wants to listen on/talk to localhost:8000? Resource monitor's Network -> Listening Ports would be able to give you some kind of indication.
Hi,
today I stumbled over this project and gave it a try:
when I start it, my Chrome browser opens up the page to authorize Spotify.ahk. I confirm this, but then the page loads forever and Spotify doesn't show up in the browser tab. I guess that's not normal, am I right?
Second, in my user account I can see that Spotify.ahk was successfully registered as an allowed application.
But if I open Spotify web player in Chrome manually, the shortcuts still don't work.
Is this project still working for someone? Or is it outdated?
Thanks
The text was updated successfully, but these errors were encountered: