You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A compressed version of the pages should be loaded and displayed by the reader.
Actual behavior
"The image could not be loaded" error is shown.
Crash logs
None.
Kuukiyomi version
0.3.2-8160
Android version
12
Device
Redmi 9 Prime
Other details
On turning the "ignore JPEG images", it seems to load the uncompressed, original version of the pages, thus defeating its purpose of being a data saver.
Not an expert, obviously, but If I try to manually use the resmush.it API to try and load the webpage on my browser, it seems to work fine. Which seems to indicate that there's some kind of problem while displaying the fetched image (as given by the "dest" field of the returned JSON response).
Acknowledgements
I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
I have written a short but informative title.
If this is an issue with an official anime extension, I should be opening an issue in the extensions repository.
If this is an issue with a manga extension, report it to the manga source extension project you added it from.
Steps to reproduce
Expected behavior
A compressed version of the pages should be loaded and displayed by the reader.
Actual behavior
"The image could not be loaded" error is shown.
Crash logs
None.
Kuukiyomi version
0.3.2-8160
Android version
12
Device
Redmi 9 Prime
Other details
On turning the "ignore JPEG images", it seems to load the uncompressed, original version of the pages, thus defeating its purpose of being a data saver.
Not an expert, obviously, but If I try to manually use the resmush.it API to try and load the webpage on my browser, it seems to work fine. Which seems to indicate that there's some kind of problem while displaying the fetched image (as given by the "dest" field of the returned JSON response).
Acknowledgements
The text was updated successfully, but these errors were encountered: