Hi,
The Modern PWAs display inconsistently for us. Sometimes the Modern PWA will display reasonably quick, sometimes we get a spinning circle for a long time, sometimes we get a blank screen.
I have disabled all Chrome extensions except “Clear Site Data”.
If we get a spinning circle, and we delete the cookies (or use the Clear Site Data extension), it usually displays properly on reload, but it won’t work consistently when you return to that PWA page again.
I have checked for extra fonts and am using the “Latest from the Repository” option.
When it spins for a long time, I see this error in the Inspect>Console view on Chrome:
I see similar things with both Scriptoria builds (v11.3) and my local builds (v11.4.1).
I believe I have fixed the issue with the failure displayed in the first message above. It was trying to use the saved last reference which would be specific to the project.
The spinning circle appears to be fixed. Thanks!
We still get a blank page, when we switch back and forth between them.
Screenshot below, it is the same error in the console each time.
Sometimes a refresh (CTL-SHFT-R) will fix it, but not always.
If you using “Preview PWA”, you will need to use the Clear Site Data extension when you switch between different projects since they will have different contents cached.
I also used the latest repository using Scriptoria with the older SAB version, a couple weeks before that. When viewing the PWA on the live website, I did use the Clear Site Data extension once or twice. I still got the blank pages some what regularly.
Yes, and no. I am viewing the Modern PWA as more than a beta but not a finished product…yet.
We still have issues; especially if there are any books other than a book of the Bible. IE: GLO, XXL, Intro.,… OR if there is more than one collection. From conversations with Chris, there is still a lot of work that needs to be done to get the Modern PWA to really match the expectations of the actual phone apps.
Bottom line, if its only a single collection with just books of the Bible, then it seems to be working most of the time. If it has any of the other issues, we don’t even try the new PWA.
WOW, well that certainly is important to know. Our project has Topical Indexes, maps, Read through the Bible, How to Read the Bible helps, and even the Lord’s Prayer and Apostles’ Creed in the back. So, I take it, any one of these could kill the Modern PWA, right?
I’m thinking if this is the case then SAB and Scriptoria should tell us right off the bat that “This project is too complicated to use Modern PWAs. Maybe a future version of the Modern PWA process will be able to handle this project.”
