View Single Post
Old 05-24-2024, 07:06 PM   #54
Bradles
Zealot
Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.Bradles turned on, tuned in, and dropped out.
 
Bradles's Avatar
 
Posts: 112
Karma: 35586
Join Date: Nov 2020
Location: Perth, Western Australia
Device: Apple Books & Kobo Libra H20
Yeah, you're not the first user to face this issue...

I did some more research and found that LibraryThing returns no results if any book in the result set has corrupt data. The response code is 200 (OK) but 0 bytes are returned to LT Match and that's why I'm getting an error trying to interpret 0 bytes as if it was data. I can handle this scenario better in terms of showing a more informative error message, but that doesn't help you much.

I've reached out to the LibraryThing developers, to see if the situation can be improved from their end. I'm not expecting to hear back until after the holiday weekend.

Update: LT Support are not able to offer support as the LT APIs are "officially" disabled (but really only not supported) while they work on the LT redesign. (5 years and counting.)

Last edited by Bradles; 05-28-2024 at 06:57 PM. Reason: Response from LT Support
Bradles is offline   Reply With Quote