View Single Post
Old 04-17-2012, 03:53 PM   #19
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 7,645
Karma: 5433388
Join Date: Nov 2009
Device: many
Hi,

I did find one other interesting thing that was wrong in common with both. The metadata have Amazon ASIN values that are completely incorrect.


Key: "ASIN"
Value: "543e6717-faf7-4331-9ea2-25733abea6bc"

Key: "ASIN"
Value: "33a9a718-efdb-4687-b064-9b9ba3522c71"


Since the ASIN is how Amazon devices sync across platforms, use of uuid in place of the correct ASIN might cause a problem with any device that tries to sync with a strange formatted non-ASIN. (ie. ties to sync pages across devices).

ASIN's should not be made up nor should they be UUID strings.

Please delete the ASIN metadata values and see if that does the trick.

KevinH
KevinH is offline   Reply With Quote