Live data from Hacker News

Apple Photos app corrupts images

tenderlovemaking.com

161–170 of 471 posts

Re: Apple Photos app corrupts images

#162

Your workflow was horrendous, and now it's merely bad. Don't touch any images on the card until you're sure that the images imported correctly AND your local and cloud backups have backed up the images. I assume you have local and cloud backups. If not, you should set them up right away. Really, cards hold a huge number of images and there should be no rush to empty them out.

That the workflow could be better does not really excuse the software corrupting the images. This is like the "you are holding it wrong" type excuse.

Re: Apple Photos app corrupts images

#163
post #157

I've not experienced corruption like the author, since my workflow involves copying the raw files from sdcard to harddrive, and then importing into Photos. After processing the raws in Photos, I export a .jpg back out to the filesystem. That's because my worry is corruption of the entire Library, which Photos stores as one gigantic opaque file/directory abomination. My .photoslibrary file is currently 70gb in size, a…

Photos uses sqlite. I came across this but haven't tried them yet. https://github.com/AndrewRathbun/iOS_Photos.sqlite_Queries

Re: Apple Photos app corrupts images

#164

I am not letting Apple Photos touch my photos. Neither Google Photos, etc. All my photos are managed using Digikam and developed using Darktable. They are also visualized via immich, but immich only has access via a read-only mountpoint. Everything is hosted locally of course.

I am moving this direction, but for now as a redundancy purpose. Copied google take out into immich, who has its mountpoint use truenas iscsi backed by zfs. Zfs is set to take snapshots frequently.

Re: Apple Photos app corrupts images

#165
post #87
post #30

> Turns out “delete after import” was a huge mistake. That's a mistake no mater what application you're importing to, else we'll be graced with another blog post, "Darktable app Corrupts Photos". What's the purpose of RAW+jpg though? Seems rather redundant?

Speed. It all comes down to speed. Processing RAW can be expensive time wise. If you’re sorting through a session of 10,000 photos, you want the speed that comes with the jpeg variant, which allows you to quickly sort out blurry, smeared, severely mis-exposed, and other various defect photos. The storage cost is negligible (JPEG75@10MP is cheap) and the workflow benefit is immediate. Additionally, cropping and early…

> Speed. It all comes down to speed.

GP isn't wrong though. Most cameras embed a medium quality full-resolution JPEG along a couple different thumbnails in raw files, so saving raw+normal JPG is kinda pointless, because the raw already contains that jpeg. Raw+jpg is only easier in the sense that many/most non-vendor tools - even viewers - can't properly handle the embedded jpg so it's easier to just duplicate the storage (e.g. 50 MB for the raw + 10-20 MB for the JPG) and take the hit on storage consumption/transfer time.

Re: Apple Photos app corrupts images

#166

I’m a fan of the whole Apple ecosystem but I have to say that there’s a pattern here. Apple does a decent job of keeping my data safe from others but a terrible job of keeping it intact. From music libraries with song titles that got switched to long integers to this (and I’m sure more that I’m not remembering atm) they need to do a better job here. Sure security is important but integrity is too.

I stopped using apple's notes app with an ipad pen after it lost 20 minutes of my handwritten notes when trying to sync them. (Which fits the theme of apple losing people's stuff.)

I don't really get the syncing situation with apple. And it's really hard to tell when they've resolved bugs in one app or introduced new ones elsewhere.

The Safari reading list can't even sync properly between devices for me. Image Capture ("Keep Originals"??) or AirDrop is a little minimal for such a keystone part of the phone -> computer if you don't want to use Apple ecosystem after.. Let alone the other more complicated issues.

Re: Apple Photos app corrupts images

#167

Earlier quoted context omitted.

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…

They asked me for a sysdiagnose when I complained about how crappy their new Finder disk icon looks on macOS 26. See this rant by Jeff Johnson, who called for a boycott on filing bugs with Apple a couple years back (I stuck to the boycott except for two obvious UI design issues in the latest OS because neither required repro steps (so why the sysdiagnose?)).

https://lapcatsoftware.com/articles/2025/8/7.html

Edit: accidentally called sysdiagnose a spindump.

Re: Apple Photos app corrupts images

#168
post #124

Earlier quoted context omitted.

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…

how is this different from any product with a billion users and 100,000+ live bug reports? I've had pretty good luck reporting bugs to Google (notoriously bad!): 1. provide simple, crystal clear examples that cannot be due to third parties, misconfiguration or user error. 2. show that it's happening to a large number of mainstream users (not niche) 3. show that it breaks critical workflows and has no easy workaround…

[dead]

Re: Apple Photos app corrupts images

#169
post #81

Earlier quoted context omitted.

Sounds like an argument for Apple to provide a new high-level media import framework?

Why? A new framework gets you new bugs instead of the old ones, but not necessarily fewer or less severe ones. It’s more likely that things will be reversed: the old, battle-tested framework may have bugs, but it’s is less likely to have serious ones. They should try to hunt down bugs in the existing code. A partial rewrite of parts that historically have many bugs may be in order, but a complete replacement? Unlikel…

Well I'd imagine the new framework wouldn't rewrite old but wrap the existing low level APIs in a way that is not error prone. Centralize the tricky bits so Photos and third party apps don’t each have to reinvent them?

Re: Apple Photos app corrupts images

#170

I’m a fan of the whole Apple ecosystem but I have to say that there’s a pattern here. Apple does a decent job of keeping my data safe from others but a terrible job of keeping it intact. From music libraries with song titles that got switched to long integers to this (and I’m sure more that I’m not remembering atm) they need to do a better job here. Sure security is important but integrity is too.

[flagged]
Post reply on HN