Marijn Pessers
Marijn Pessers
I struggled a bit with this myself. It was quite annoying, every 10 minutes a new popup, but I wrote here what I found worked for me. https://community.spotify.com/t5/Spotify-for-Developers/INVALID-CLIENT-Invalid-redirect-URI/m-p/5338762/highlight/true#M4036
> I fixed this by choosing a different port to 80; for whatever reason when chrome opened up the callback it would drop the :80 extension to the URL even...
Quick note; make a backlog item that the head section (page title) can be modified without interop when .net5 is released.