Skip to content

amazon fails with status 400 (new setup) #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
dfaulkner opened this issue Jan 10, 2017 · 4 comments
Open

amazon fails with status 400 (new setup) #129

dfaulkner opened this issue Jan 10, 2017 · 4 comments

Comments

@dfaulkner
Copy link

Running Tomahawk nightly (0.8.99) from Ubuntu PPA: version 0.8.99.20160426422+12ubuntu16.04.1
Running on Linux Mint 18.1 Serena.
Tried the amazon resolver as the nightly axe file and the git repo. Same results.

Putting in a username & password, I get the error message: "Your config is invalid."
Watching a terminal log, I see "Function not found: _testConfig"
When I restart Tomahawk, I get the following messages (line breaks added for readability-original is single line):

"Failed to do nativeAsyncRequest"
"Status Code was: 400"
"Amazon Music failed login: {"contentType":"text/html",
    "readyState":4,
        "response":"<html>\r\n<head><title>400 Bad Request</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>400 Bad Request</h1></center>\r\n<hr><center>Server</center>\r\n</body>\r\n</html>\r\n",
    "responseText":"<html>\r\n<head><title>400 Bad Request</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>400 Bad Request</h1></center>\r\n<hr><center>Server</center>\r\n</body>\r\n</html>\r\n",
    "responseType":"",
    "status":400,
    "statusText":"400 Bad Request"}"
@theli-ua
Copy link
Collaborator

weird, works for me
What amazon region are you using?

@dfaulkner
Copy link
Author

dfaulkner commented Jan 12, 2017 via email

@theli-ua
Copy link
Collaborator

It works for me with master tomahawk and US region.
iirc ppa version is stale and thats the most likely reason

@dfaulkner
Copy link
Author

dfaulkner commented Jan 12, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dfaulkner @theli-ua