Apple Photos app corrupts images

It seems to be an import pipeline bug.

Photos does a lot of extra work on import (merging RAW+JPEG pairs, generating previews, database indexing, optional deletion), so my guess is a concurrency bug where a buffer gets reused or a file handle is closed before the copy finishes.

Rare, nondeterministic corruption fits the profile.

This is also my guess. It's really a bummer, and I'd report it to Apple but since it's nondeterministic I have no idea how to provide repro steps.

I have had extremely bad luck, reporting bugs to Apple.

They constantly ask for an example project, even if it's something that is easily demonstrated, simply by running existing Apple software, and creating a project, would be a huge pain.

They also ignore reports. Very rarely, I may get a ping on one of my reports, asking me to verify that it was fixed in some release. Otherwise, there's no sign that they ever even read it.

I usually end up closing my bug reports and feature requests, after a few months, because I'm tired of looking at them.

It's clear that they consider every bug report to be a burden. That's a very strange stance, but then, they are not a typical company.

I guess you can't argue with the results, as they have a market value North of 3 trillion dollars, but that does not make it any less annoying.

Not to hand wave-- but this feels industry standard IMO. I have a dozen PRs sitting unacknowledged and stale across a handful of FAANG (and other) repos, including Apple's.

I start my first day @ Apple in a few weeks, so I ACK that my opinion might be a little biased here.

If you ever get the chance, maybe you can be the one that improves that process some day.

Even if it's standard among tech giants, you could be the one that makes a new standard! Good luck in your new role, btw.

Unless one's title is going to be "VP" or "SVP", the chance that someone joins BigTech and gets to "improve the process" is usually miniscule. You're being hired as cog #21 on team #54 and there is a large backlog of JIRA (well, in this case, Radar) tickets to grind through. There will be people who tell you what the processes are, and to not deviate from them. And you shouldn't get mad at those people, either--they're just the messengers, and were told what the processes are by people above them on the totem pole and so on.

More than once I've had a chance to interview (brief) somebody who was about to take a job at a "big tech" company and interview them again (debrief) after they left.

Frequently they were excited to start work at a place where they could "make a difference" and within a year they came to the conclusion that there's wasn't any possibility they could make a difference.

Organizations of that sort have no interest at all in hiring people who aren't going to cooperate on their process.

If they were excited to make a difference at a big tech company and gave up in a year, it sounds like they didn't understand what they were getting into at all. Goals take time.