Thread: Error sending metadata to device
View Single Post
Old 09-17-2016, 10:16 PM   #9
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Terisa de morgan View Post
It is reported in the extended device thread. It looks like it only happens when you are sending a big batch of books to the Kobo (it has happened to me too), but no further damage.
The code that is failing is a check in the database for an imageId. If all the books have one, then the update is not run and hence this is error not seen.

The imageId is usually missing for book formats that don't have a format. TXT is the usual one I see. But, it is also not created if a kepub doesn't contain a cover. The extended driver is fixing this so that if a cover is sent separately, it will be used.
davidfor is offline   Reply With Quote