Skip to content
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.

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

Update failed: The anime is already in the list #328

Closed
devfabiorm opened this issue Nov 3, 2016 · 8 comments
Closed

Update failed: The anime is already in the list #328

devfabiorm opened this issue Nov 3, 2016 · 8 comments

Comments

@devfabiorm
Copy link

devfabiorm commented Nov 3, 2016

6a8edd92-a158-11e6-93b0-406661df2373

I don't know to what this id refers to, but there is no anime with same title in my list.

@devfabiorm devfabiorm changed the title Update failed: The animes (id: 33075) is already in list Update failed: The animes (id: 33075) is already in the list Nov 3, 2016
@erengy
Copy link
Owner

erengy commented Nov 3, 2016

From what I can see, the anime is in your list, which is why MyAnimeList returns that error. I imagine that either something went wrong with the MAL server while updating your list, or you'd already added the same anime via the website previously.

In any case, you can delete Musaigen no Phantom World Special from the update queue of History page, and then synchronize your list to get rid of the issue.

@erengy erengy changed the title Update failed: The animes (id: 33075) is already in the list Update failed: The anime is already in the list Nov 3, 2016
@erengy
Copy link
Owner

erengy commented Nov 3, 2016

This turned out to be an error on MyAnimeList's part.

@louisch
Copy link

louisch commented Nov 3, 2016

So I'm guessing that now we're waiting for MAL to respond to that thread, because there's a chance they'll revert the API?

@erengy
Copy link
Owner

erengy commented Nov 3, 2016

Exactly. In the meantime, you may use the latest build, which is able to handle the changed behavior. If they don't revert it, I'll release an update within a few days.

I almost don't want to complain, because they actually fixed something in the API, even though it broke backwards compatibility. :')

@louisch
Copy link

louisch commented Nov 8, 2016

Just to give you my own opinion, I don't really mind if I'm forced to update. I'm already using the latest build at this point, which works a treat. I think if the API is better then it would be best to just keep it.

@erengy erengy closed this as completed in 0d4927f Nov 9, 2016
@Nur-Kekse-im-Kopf
Copy link

Just to make sure - this hasn't been resolved with the recent Taiga update (1.2.5 I think) and still depends on MAL to do whatever on their side? I am asking as the error still occurs and I wasn't sure whether the update had something to do with it.

Best regards and all :)

@erengy
Copy link
Owner

erengy commented Nov 12, 2016

What happened was that MAL API suddenly started giving an unexpected response to Taiga's add-anime-to-list requests. This caused Taiga to interpret the new response as failure, even though MAL actually added the anime to user's list. This issue (the "Created" error) is resolved in v1.2.5. However, if you have an anime in your update queue that gives you the "The anime is already in the list" error, you still need to remove it from History page and re-synchronize. Because, the anime is in your list, so the error is appropriate.

@Nur-Kekse-im-Kopf
Copy link

I see. Thank you very much. This helped. It seems, I had to look a bit longer to find all instances of that anime in my history list (and, well, there was a search window all that time ... I just didn't notice :D )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants