FolioReader / FolioReader-Android

A Java ePub reader and parser framework for Android.
BSD 3-Clause "New" or "Revised" License
2.25k stars 718 forks source link

White screen after page loader #321

Open iLeafSolutionsPvtLtd opened 5 years ago

iLeafSolutionsPvtLtd commented 5 years ago

Issue / Feature - Some times it takes long time to load the content and sometimes white space comes when progress bar disappears FolioReader version - 0.5.1 FolioReader Stock / Modified - Slightly modified, Android SDK - 27 Mobile / Tablet / Emulator Info - mobile Crash / Error - We have upgraded to the latest version of Folio Reader and it works fine except some scenarios. Sometime Folio takes too much time to load a book and sometimes just white space comes after loader. If you keep it like that without much interaction book may load in 4-5 seconds. Another issue is with the configuration window, if you change font or size in quick succession the UI freezes and ends in ANR.

Steps to reproduce / Describe in detail - You can reproduce the white screen by opening and closing multiple books or by keeping a book open for some time and then do a bit page scrolls

hrishikesh-kadam commented 5 years ago

White screen issue has been fixed by this commit https://github.com/codetoart/FolioReader-Android/commit/4e72aae1632517594eaaa6d6ae69b6f3d9525c6e, which will get released in next release. Also that would decrease loading time in some amount.

For ANR while font and its size change, it would be better to open a new issue. That would help us to track issues better. Let us handle one bug by one issue.

iLeafSolutionsPvtLtd commented 5 years ago

Okey... Thanks anyway...

iLeafSolutionsPvtLtd commented 5 years ago

We are eagerly looking forward for your latest release.It would be great if you can give an update on the release.Thanks in advance

hrishikesh-kadam commented 5 years ago

@iLeafSolutionsPvtLtd Fix for this issue is released in version 0.5.3

iLeafSolutionsPvtLtd commented 5 years ago

As you said we tried both 0.5.3 and 0.5.4 . But both seem to have issues with configuration changes. We can't publish our app update until it is fixed.