Musish
Musish copied to clipboard
BUG: Login never completes
Describe the bug I can't login. Using two factor authentication the popup login window stays blank white and never logs me in.
To Reproduce Steps to reproduce the behavior:
- Click Login
- A popup window appears
- Enter Apple ID and password
- Enter 6 digit code from two factor authentication
- Window is loading, then stays white, no login happens
Screenshots

Console error message when the white screen happens:

System I use:
- OS: macOS 10.13.6
- Browser Safari 12.0.2
It might be a MusicKit issue, I tried playapplemusic.com and the same white screen happened on the login screen with the same "Unrecognized token" error message in console, using latest Safari on macOS 10.13.6
I got the same Error. The translation file seems to be broken, which contains no JSON: https://authorize.music.apple.com/locales/de-at/translations.json?_=1548257054572
The de-de variant seems to be fine:
https://authorize.music.apple.com/locales/de-de/translations.json?_=1548257054572
I can confirm it works on Chrome 71 (Mac)
A quick workaround is to change your browser's language. In my case my language setting was set to de-AT when i switch to de or de-DE that translations file was loaded correctly.
After musi.sh has been authorized you can revert your changes to the browser language.
I have the same issue in Chrome 73.0.3683.103, the console log error is as follows:
SyntaxError: Unexpected token < in JSON at position 0
at parse (
@c0defre4k you are the man, you actually probably just helped me finally be able to figure out / close this one ticket I could never figure out why on earth just users from the Germany / Austria area were having all these login problems with apple and nobody else would ever report them. I have the email of the dev who coded most of the musickit library because we got early access to the docs, I'm for sure going to let them know to at least put {} in the translation files that have no translations.
@RiFi2k that sounds great. I hope they fix it, because thats pretty annoying.
I don't know if {} is sufficient. Maybe they should implement some fallback logic to respond with some default translations.
I feel like if its getting tripped up at json parse, technically {} should keep it from throwing an error there, unless I'm wrong I never actually tried. There is a good chance it will get done, I can have someone from a big company that starts with S get on their case about it because it for sure has to be our login issue.
This issue actually got forwarded to the apple devs today because of my day job, so fingers crossed.
This issue actually got forwarded to the apple devs today because of my day job, so fingers crossed.
Is there any information when they will fix it? Apparently its not fixed yet, error still occurs.
+1