search

5-stones / react-native-readium

📚 📖 React Native ebook reader for iOS, Android, & Web via Readium
MIT License
83 stars 25 forks source link

Android: Lag in Applying User Preferences When Reopening Reading Module #62

Closed amalStorilabs closed 1 day ago

amalStorilabs commented 1 month ago

When we repeatedly open the reading module by going back and reopening it, there is a noticeable lag on Android when applying user preferences, such as font size and appearance. The settings initially display the default values before transitioning to the user-specified preferences. This issue is specific to Android, as iOS provides a visual indication with a loader until the page is fully rendered. I've verified that the settings variables are correctly set in the React Native code, so it appears to be an Android-specific issue.

jspizziri commented 1 month ago

@amalStorilabs, what version of the library are you using?

jspizziri commented 1 month ago

@amalStorilabs , please see my question above, also please document steps to reproduce this within the example project. If I don't hear back from you in a couple of days I'm going to close this issue.

jspizziri commented 1 month ago

closing due to lack of response.

amalStorilabs commented 4 weeks ago

Sorry for the delay in response .

Steps to reproduce 1 . Open a book

  1. Change the appearance/theme of the book
  2. Click back to exit from book
  3. Click again to enter the book
  4. When 3 and 4 are repeated continously there is a lag in rendering the book with the changed appearance , it first shows the default appearance then after sometime only the changed appearance is shown

NB : This only happens in android . I am using react-native-readium@1.0.4

You can also download my app from playstore and access free books to see this issue happening https://play.google.com/store/apps/details?id=com.velichamtech.wordrobe

I am using this fork to install the package : https://github.com/WordrobeBooks/react-native-readium

please have a look into this Thanks

jspizziri commented 4 weeks ago

@amalStorilabs thanks for the response. No worries on the delay, opening this back up. A few follow up questions:

  1. Are you able to reproduce this issue in the example app in this repo?
  2. Have you tried upgrading to the latest RC to see if there are any improvements?
jspizziri commented 1 day ago

Closing this issue due to lack of response.