gmusic-playlist.js icon indicating copy to clipboard operation
gmusic-playlist.js copied to clipboard

403 Response

Open Fuelsean opened this issue 9 years ago • 2 comments

EDITED Logged into multiple Google accounts. After switching to a different account it seems to be using the wrong account into.

Steps I took: Logged into account A, exported playlists. Switched to account B, imported playlists. Calls to play.google.com are returning a 403 response for both search and createplaylist.

After logging out of account A and back into account B, import worked fine.

alt-svc:quic=":443"; ma=604800; v="30,29,28,27,26,25" alternate-protocol:443:quic,p=1 cache-control:private, max-age=0 content-encoding:gzip content-length:117 content-type:text/html; charset=UTF-8 date:Wed, 06 Jan 2016 17:30:54 GMT expires:Wed, 06 Jan 2016 17:30:54 GMT server:GSE status:403 x-content-type-options:nosniff x-frame-options:SAMEORIGIN x-rejected-reason:OTHER_AUTHENTICATED_USER x-xss-protection:1; mode=block

Fuelsean avatar Jan 06 '16 17:01 Fuelsean

I am able to reproduce the issue if I switch accounts in the google music webapp without also changing the chrome user.

If I switch to either incognito mode, a new non logged in chrome user, or login as the user I am accessing google music under, I no longer end up with the forbidden requests.

Fuelsean do you think that's what you are seeing?

I can see if I can detect this case and at least issue a warning; ie (You are signed in to Chrome as A but signed in to Google Play Music as B. To import/export playlists, sign in to Chrome as B) This would be similar to the warning that appears when attempting to upload songs in this case.

soulfx avatar Jan 07 '16 00:01 soulfx

Saw this too as well - when logged into an additional account - https://play.google.com/music/listen?u=2#/now - then the script doesn't work. Incognito mode, just one account logged in, worked fine.

chrismo avatar Jul 23 '16 18:07 chrismo