TheNetsky/extensions-generic

HentaiFox - Random pages cannot load

Closed this issue · 6 comments

Describe the bug
For a number of manga titles from the HentaiFox source, random pages (particularly near the final few pages but sometimes other random places) will fail to load. On the new Paperback reader view, these pages just appear black. If you use the Legacy Viewer, it explicitly says "Failed to Load".

To Reproduce
Steps to reproduce the behavior:

  1. Add the latest Bentai tracker.
  2. Add the HentaiFox source.
  3. Open random different manga to test this error. Not every single one does this, but many do.

Expected behavior
The source should load all pages of the manga without error. All failed loaded pages were also double checked on the HentaiFox website directly to ensure the pages are actually there. They appear on the site, but fail to load within the app only.

Screenshots/Video
image

App version

  • v0.7-r46

Source WITH source version

  • HentaiFox 1.1.0

Additional context
It was mentioned earlier, but if you find a manga with pages that fail to load, generally I have found they have no problem loading on the website itself. It doesn't seem to be a matter of missing pages or broken images, more so that the source isn't loading some pages for whatever reason.

If even a page or two isn't loading at all, it also will fail to download a local copy.

Going to need specific titles.

Sure thing, here's a few:

• Icha Love Nikushoku Girl - Lovesick Girls of Beast (Author: Hinahara Emi) [Halfway in, a large chunk of pages fail to load]
• Koibito Doushi + Motto Koibito Doushi 1&2 (Author: rico) [One of the last pages does not load]
• Ikenai! Ohimesama (Author: koume keito) [One of the last pages does not load]

More common is one of the last pages not loading, taking out the ending pages of a manga. Less common (but still only really happening with this source) is the first title, where literally a large chunk of pages will not load from any point, making the entire title unavailable to download.

Already know the cause.

Something from my setup or something fixable from the source itself? It's good it's easily spottable at least.

I gotta fix

Cheers, thank you.