There was an error writing metadata for keywords
In Bridge 184.108.40.206 / 220.127.116.11 on Mac OSX Mojave 10.14.3
some jpeg files cannot be assigned keywords. I get the following message 'there was an error writing metadata to xxx.jpg'. Files are either located on the local HD (APFS) or an external HD (USB-C HD HFS+).
I tried to purge the cache several times as advised on forum threads, installed various versions of Camera Raw (10.X 11.X and 12.X) to no avail. I even reverted back to Bridge 18.104.22.168 but the error persists. This is pretty frustrating. Hope this can be fixed easily. Thanks !
Win 10 pro, most recent Bridge update, pscc 2020. same problem. cannot add metadata, keywords, title, description, etc. this problem has evidently been around for 15 years - time to do something, Adobe!!!
The error message is pretty consistent. It seems to happen about 50% of the time. Most of the time when the error is displayed it takes several attempts for the metadata to be saved.
I typically assign several key words to a picture, and sometimes it on the first item, sometimes on the 2nd or 3rd item.
Mike Bowen email@example.com
Frank Bruno commented
I am having this error as well. They need to put some basic error catching into the Keyword/metadata function. It is ruining files...
Michael Jackson-Rand commented
This is still an issue and as mentioned above obliterates the usefulness of Bridge. As a core capability of Bridge being a local asset manager, it is woeful to think that keyword assignments are the Achilles heel.
Hello, is it only some files? are they peculiar (CYMK 16 bits, very large?) could you share and attach one here?
I had the case when no stars would be written, but ACR had that image open in another screen...
I had the issues in the past with video files.
Eugen Naiman commented
I have the same problem and my apps are at the latest version (CC subscription) On my local hdd on each folder some *.jpg files will throw the same error when trying to write metadata.
I have tried everything I could, including clearing cache, running Bridge as administrator, changing files ownership and permissions and nothing helped.
PhotoMechanic is having no problems at all and once I add a keyword in PhotoMechanic to a file, Bridge will happily do any changes ... it's like PhotoMechanic is flipping an invisible switch.
It would be really good to have this bug fixed.
This is a major problem for anyone affected as it effectively stops you using Bridge. Unbelievably the retired Windows Photo Gallery is easier to use and more reliable.