very-doge-wow / amazify

Flask app for automatically migrating Amazon Music playlists to Spotify.
1 stars 0 forks source link

Internal Server Error #27

Open Kaseax opened 2 months ago

Kaseax commented 2 months ago

Hey! Just wanted to give the app a try. Everything works, but if I click on the last button, I'll get a "Internal Server Error"

image

cc @very-doge-wow

very-doge-wow commented 2 months ago

Hi, the error message indicates that the amazon user object couldn't be retrieved. Have you set up the Amazon OAuth as described in the Readme?

I also haven't tested the app with Python 3.9, I was using 3.11.

Kaseax commented 2 months ago

Yes, I did just like that. Clicked on "Get Token", logged in and copied it.

very-doge-wow commented 2 months ago

Just tried it myself and it indeed seems to be broken... This is the response by the amazon API:

{"status":401,"code":"INVALID_CLIENT_ID","message":"Unable to identify client. Check the x-api-key header.","reference":"4d8efdc0-22ed-4a24-87d0-839a9b048495"}

It may very well be that the workaround using the generated token by the interactive API reference has been patched and doesn't work anymore 🙁

I'll have to do some more debugging when I get to it...

Kaseax commented 2 months ago

Okay, that's sad. So there's no way to use your app at the moment anymore?

very-doge-wow commented 2 months ago

Actually I believe it's a bug in the interactive API reference, which seems to issue invalid x-api-key headers. I think that's the reason because even when using it directly, it returns the same message:

Unbenannt

So yes, the app can't be used at the moment unless amazon fix the API reference.

very-doge-wow commented 2 months ago

Sadly the Amazon Music API is still in beta stage and no official support is available. I have however created a new thread in the Amazon Developer Forum. I would not however get my hopes up, as activity seems to be quite low there...

very-doge-wow commented 2 months ago

Unexpected answer from Amazon:

The dashboard isn't supposed to be publicly available as the API is still in beta stage. So the fact we were able to use it was rather by mistake and I don't think they'll employ any effort to fix it for us. 😞