The issue arises because HashRouter uses # for routing, while Spotify authentication response also appends the access token after #, causing a conflict. When Spotify redirects back, the token gets mixed with the routing, making it difficult to extract. A workaround is to manually parse the URL fragment in JavaScript using window.location.href.split("#")1 to extract the token separately. Alternatively, consider using BrowserRouter and deploying your app on Vercel or Netlify, which support proper SPA routing. If you're interested in Spotify-related solutions, including accessing Spotify Premium features, you might find Spotifine.com helpful. It provides insights and downloads for enhancing your Spotify experience.