In an earlier thread (not mine) it was mentioned that if you operate with no other apps in memory (my policy), and then open one of the Logos apps, it then begins to (again) build your library list. If you quickly type in a filter (e.g. LEB) while it's building the library (with the user assumption that you're narrowing down what you really want 'fast'), you end up with NOT that resource.
It's really quite fascinating to watch. In a previous query/install, it had decided I should have the ESV (why I don't know) and I over-ruled it with the LEB. In the meantime it got all mixed up, tried to read the ESV offline when only the LEB was downloaded, and eventually showed nothing. I refused to re-install, so we came to a 'draw'.
With the update, it gave up on the ESV. But interestingly refused to show the LEB either (really mad!). So online, all the Lexhams were displayed but no LEB. Offline, the LEB was the ONLY one displayed (and only one downloaded).
It's obvious to me, the library query assumes the user is going to quietly wait for all 3500 volumes to load; else if interupted (1) it gives up at that point and can't be induced to continue and (2) looses track of what the user already has installed.
Not looking for a work around, etc. Just reporting the fascinating coding. I'm learning to (1) stay offline and (2) avoid updates/re-reads of the library.
