Broken export under macOS for a few months now

Not that reporting anything here fixes any issues ever

By @Toastman3000

Actually, reporting here does fix stuff. When a public report in the Bugs section is fixed, two things happen:

• The public report in the Bugs section gets its status updated, for example you can see Adobe-assigned statuses there like Acknowledged, Investigating, and Fixed.
• When one of those bugs is fixed, the public release notes for the version that fixes it includes a link back to its public report in the Bugs section, so that anyone can trace it back.

Adobe isn't perfect, but what they do there is actually a lot more public accountability than we see from many other companies who never even publish bug reports in public form.

The problem here is isolating what exactly is causing the problem so that it’s easy to reproduce on any other computer, like a test machine at Adobe. Because like others here, my macOS 13 Mac exports from the latest version of Lightroom Classic all the time without problems. But, although I do use a couple of cloud sync servces, I don’t use the option that evicts files from local storage to the cloud. Those can be tricky, in fact Apple had some major bugs recently with that feature in iCloud Drive that they finally fixed. I don't work at Adobe but I can imagine a situation where the sync service is starting to evict files to the cloud and so maybe when Lightroom Classic goes back to verify its exports, it finds only a dataless placeholder when it was expecting for example an 810K JPEG image, and calls that an error. Some applications don’t yet know about the dataless placeholders used by cloud services that evict local files.

I am not saying that is the cause, because I don’t know. My main reason writing that last paragraph is to maybe point Adobe to how to reproduce the problem, if in fact it is related to using a cloud sync service where the feature is enabled that leaves behind only dataless placeholders locally.