I have many photos on the cloud, which wasn't a problem before this update. It didn't affect me.
That is exactly the issue - the files can persist in the filesystem at some level below the Photos database and we may never know it. That might explain why deleting photos doesn't always free up storage.But that is also how backups work, it copies everything and then restores everything, it didn't have much bigger issues.
Edit: I should add one point here and with this bug, the files were not fully marked for deletion which is most likely why they got backed up.
A grand total of none, because encryption keys.I wonder how many phones were traded in where the user wiped the phone (e.g., erase all content and settings) prior to trading it in or selling it, that now have this problem?
What do you mean not satisfactory? It makes perfect sense.Really not a satisfactory response from Apple's side. I guess we'll never know the whole truth.
I don't even have any photos on iCloud, so not concerned, but this is just a paper thin excuse.
Apple only has a small* number of users to begin with.With Apple being Apple, it’s always “a small number of users”.
I'd like Apple to say that they have a way to purge the photos database of the deleted photos. What else wasn't deleted but is only hidden?Huh? What else do you want them to say?
This is all there is to the story. I know because somebody on Twitter posted the actual code change made with the update fixing this bug.
No, we don’t know all we need to know. In particular, Apple hasn’t stated whether they consider photos persisting after deletion a bug, and have fixed that, or only the resurfacing of such persisted photos.If you’re into conspiracy theories, then no. Otherwise - you now know pretty much all you need to know.
How to tell us you don't understand the bug without telling us you don't understand the bug.I'd like Apple to say that they have a way to purge the photos database of the deleted photos. What else wasn't deleted but is only hidden?
If they actually erased the device, zero of the trade-in devices would have this problem, unless the new owner’s backup suffered from it.I wonder how many phones were traded in where the user wiped the phone (e.g., erase all content and settings) prior to trading it in or selling it, that now have this problem?
No way. If the link was removed, even the OS would not be able to see the file. You would need special recovery tools to scan the storage to find the blocks with data and try to restore tzhe files. How could a software bug restores those files?Sounds a lot like deleting files on a typical file system where only the pointer is removed (so you can't see it) but the actual file is still physically on the disk (until overwritten)
Let me see if I can find some more hairs for you to split.No, we don’t know all we need to know. In particular, Apple hasn’t stated whether they consider photos persisting after deletion a bug, and have fixed that, or only the resurfacing of such persisted photos.
We also don’t know whether such persisted photos for which the undeletion hasn’t been triggered yet continue to be present in the corrupted database, or whether all such corruption has been fixed and all deleted photos now truly deleted by the update.
And there is the bug, the pointer didn't fully get removed from the database.No way. If the link was removed, even the OS would not be able to see the file. You would need special recovery tools to scan the storage to find the blocks with data and try to restore tzhe files. How could a software bug restores those files?
See https://forums.macrumors.com/thread...surfaced-deleted-photos.2427262/post-33160917.I was calling out Apple for being quiet on the issue but this response is enough. I believe the explanation and don't need anything further.
To those asking for more, what else do you want?
The issue was with local storage. Why would having more of it help?
Thanks for that info. It is concerning, because it means the photos were in non-deleted files on the file system, and likely still are, and such “deleted” photos will continue to be transferred through backups and device migrations indefinitely.Here’s what happened:
![]()
Here’s why deleted iPhone photos returned to some iOS devices
Apple finally elaborates on the “database corruption” issue.www.theverge.com
OG analysis:
![]()
Inside the iOS bug that made deleted photos reappear
Getting the updates For this analysis, we will use the iPhone 13 as an example to compare the changes made between iOS 17.www.synacktiv.com
I wonder how many phones were traded in where the user wiped the phone (e.g., erase all content and settings) prior to trading it in or selling it, that now have this problem?
Everything is present on the disk until something else overwrites it this is how storage works.
I have many photos on the cloud, which wasn't a problem before this update. It didn't affect me.
This bug inflates the amount of storage used on the iPhone.
Deleted photos were not being deleted. Most users simply transfer backups from one phone to another and have been doing so for years.
This helps Apple sell more storage.
It is obvious more explanation is needed
You can still restore files from a system even after they are deleted from the file system table. The only time you can't in modern times is if you change the hardware encryption keys. And this is the root of this bug the rows were not fully deleted from the database so the files persisted....
Not really. When files are encrypted, they stop being present as soon as the key is erased.
....
Because backups are normally mostly deltas and not full backups.The whole deleted files and restore doesn't really mesh with me as surely backup size would be absolutely huge?
So, you don't understand it.How to tell us you don't understand the bug without telling us you don't understand the bug.