I have a bunch of pictures (22 to be more precise), all of them taken with an iPhone SE that return an error when Digikam tries to write to its metadata. The thing is, they already contain some metadata, so in the past they could have been written correctly. But it's just a fraction of all the pictures taken with that device (22 out of 3212).
Coincidentally, pictures taken with that device (iPhone SE) are the only ones in my library affected from the bug
https://bugs.kde.org/show_bug.cgi?id=372340 where face regions are mispositioned on vertical pictures if they were tagged from another software.
Anyway, in the debug window, I can read the following:
Digikam::MetadataHub::writeTags: Writing tags
Digikam::MetadataHub::writeTags: -------------------------- New Keywords ("Restaurant", "test", "Joe's Shanghai", "New York")
Digikam::MetaEngine::setIptcKeywords: "/media/sshfs/box_ext/mnt/md0/Personal/User2/FOTOS/2018-12 Nova York/IMG_0374.JPG" ==> New Iptc Keywords: ("New York", "Restaurant", "test", "Joe's Shanghai")
Digikam::MetaEngine::save: MetaEngine::metadataWritingMode 3
Digikam::MetaEngine::save: Will write Metadata to file "/media/sshfs/box_ext/mnt/md0/Personal/User2/FOTOS/2018-12 Nova York/IMG_0374.JPG"
Digikam::MetaEngine::Private::saveOperations: wroteComment: true
Digikam::MetaEngine::Private::saveOperations: wroteEXIF: true
Digikam::MetaEngine::Private::saveOperations: wroteIPTC: true
Digikam::MetaEngine::Private::saveOperations: wroteXMP: true
Digikam::MetaEngine::Private::printExiv2MessageHandler: Exiv2 ( 3 ) : XMP Toolkit error 102: Requested and existing composite form mismatch
Digikam::MetaEngine::Private::printExiv2MessageHandler: Exiv2 ( 3 ) : Failed to encode XMP metadata.
I have not submitted a bug report because I don't believe it's digikam's fault, but maybe there is something weird with how Apple uses pictures and you would like to keep in mind. Or maybe these pictures have been corrupted at some point.
In any case, it would be nice to be warned that some metadata could not be saved to the file, since they only way is observing the debug log.
Locked
