mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: ASIN B0DCHPXLXR - "Sherlock Holmes and the Telegram from Hell" is resulting in a statusCode: 500, error: 'Internal Server Error', message: "Required key 'id' does not exist in Audible API response for ASIN B0DCHPXLXR" #2598
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ZLoth on GitHub (Feb 20, 2025).
What happened?
The book "Sherlock Holmes and the Telegram from Hell" - ASIN B0DCHPXLXR is a Audible.com "Daily Deal", and I had purchased it. However, no information is coming up for it, and the metadata provider is returning a statusCode: 500, error: 'Internal Server Error', message: "Required key 'id' does not exist in Audible API response for ASIN B0DCHPXLXR" . Another book, "The Ratcatcher" - ASIN B0DW9J6R6N was able to be downloaded fine, so it appears to be a single title issue.
What did you expect to happen?
Metadata for the book is downloaded including cover image.
Steps to reproduce the issue
In Match, put in the book title Sherlock Holmes and the Telegram from Hell or the ASIN. Result is "No Results".
Audiobookshelf version
2.19.3
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
Chrome
Logs
Additional Notes
Will test with 2.19.4 when it becomes availalbe for TrueNAS Scale.
@ZLoth commented on GitHub (Feb 20, 2025):
I just tried https://api.audnex.us/books/B0DCHPXLXR, and got a error {"statusCode":500,"error":"Internal Server Error","message":"Required key 'id' does not exist in Audible API response for ASIN B0DCHPXLXR"} . So, it looks like it isn't a ABS issue.
@nichwall commented on GitHub (Feb 20, 2025):
An explanation of the upstream error is here https://github.com/advplyr/audiobookshelf/issues/3741#issuecomment-2563080179
@ZLoth commented on GitHub (Feb 20, 2025):
Acknowledged. Everything points to the metadata provider.