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
After logging in, the user is brought to the <Profile /> component and the url is set to something like https://spotify-profile.herokuapp.com/#access_token=BQBkftL1q6csOOMYZojUD...
Hitting 'Logout' from here refreshes the page with the profile still loaded. To get around this, one can navigate to any page and back to their profile to have the url reset without the access_token query present. When it's gone, the Logout button works again.
I think it's because in the server's index.js there is:
After logging in, the user is brought to the
<Profile />
component and the url is set to something likehttps://spotify-profile.herokuapp.com/#access_token=BQBkftL1q6csOOMYZojUD...
Hitting 'Logout' from here refreshes the page with the profile still loaded. To get around this, one can navigate to any page and back to their profile to have the url reset without the access_token query present. When it's gone, the Logout button works again.
I think it's because in the server's index.js there is:
and the only path back to
/
is in the Nav.js component:The text was updated successfully, but these errors were encountered: