Quote:
Originally Posted by davidfor
I don't have a PocketBook to test this. But, do they have some sort of "virtual" book? The line with the error is building a file path using data from the database on the device. One of those is a null value in the database for one of the books. That could happen if the book had some sort of different status such as it hasn't been downloaded from wherever PocketBook stores books. Or there is a special location for a particular type or source of books. I don't know how PocketBook works at all. For Kobo, they do both. Purchased books can have an entry in the database but the book is not actually downloaded, and when they are, they are stored in a specific location and the database entry has the file name, but, not the full path.
Hopefully @wold will be around and have an answer. Otherwise, I would need to see the database from the device to make a better guess.
|
What you are describing is a good potential explanation. Pocketbook can make use of different cloud solutions, their own cloud or also DropBox. There is a general potential, and was the case when run into the error, that not all books from the cloud are downloaded to the device itself and therefore probably do not have a path assigned to. A potential solution would be to ignore those books because also no annotations may be downloaded, in case the book is not downloaded. With the download also the annotation comes and is available on the reader with the book