Took them a week to respond which is a lot of time to clarify such bug.
A whole week! My god it’s a miracle society survived. Good grief.
Took them a week to respond which is a lot of time to clarify such bug.
Please, all knowing genius, explain how you know they are keeping and storing the data? Don’t spew opinions, use facts.They are giving the most vague answer and it took them a week to come up with this answer to dismiss what we all know, and that is they are keeping this data stored and don’t want to admit it. I’m calling BS on this, just like I don’t trust that company anymore. At least we know Google is actively harvesting it. My respect for Apple has tanked under Tim Cook. He’s a corp liar like the rest and little in the way of innovation to show for it. I kinda hope Apple sees some headwinds to learn their lessons. They also now offshore their support to India, adding another layer of cheapening the brand because now there is a language barrier. Steve is turning in his grave now. Thanks Timmeh!
Based on your response it sounds like you misread or misunderstood the article.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.
It’s possible. Some people don’t follow directions to wipe devices and simply sign out of iCloud and hand over the phone.yep. I knew it. never believed those people for one second where they claimed had other people's pictures.
Yes, "small" is relative. But why do you otherwise question their truthfulness? This explanation makes sense. Absent a true "wipe," which Apple says would have worked, that data is there, and we all know the indexing trigger is there. What do you think is dishonest?A damage controlled response. Never even offering a sincere apology.
“Apple claimed the issue affected a small number of user”
With Apple being Apple, it’s always “a small number of users”.
I don’t believe they’re stating the entire truth. Similar to them throttling the battery during the iPhone 6(s) era.
The encryption keys are deleted, which is effectively identical to filling the filesystem with random data. That's why Apple were saying that the person who reported doing factory reset and seeing the photos in the new user's library was just not possible ( and note that user deleted their report)SO why then during factory reset the filesystem isn't filled with zeros to destroy that data?
You assume the corrupted database was actually marked for deletion. Maybe the system still saw it as Photos data without a thumbnail, or “Other” storage.Sorry don't buy it. If the data is marked as deleted it can be overwritten and their claim that very old photos, some a few years from what I heard, are not over written over time doesn't sound plausible to me. I still think cloud services are involved but they'll never tell you if they were.
That could well be the original error - it deleted the record of the photo from the database, but the final step of deleting the file failed, so the photo vanished from the library until Apple added a cleanup step to 17.5 to find the orphaned files and show them to the user.This does not explain why certain files were not deleted in the first place, and were still present on the disk!
I wonder what else is present on the disk ?
Is the bug that you’re actually at work when it says you’re at the bar, or simply that it tells her when you’re at the bar?Meanwhile the bug that tells my wife’s Find My that I am at the bar and not at work continues to persist
Can someone explain to me, in layman's terms, what a "database entry" is, and what "corrupted" refers to in this context….
…Does this also mean that these pseudo-deleted photos were taking up storage space, locally, on-device?
So what's your explanation then?Apple making things up as they go and the gullible people believe this lie
SO why then during factory reset the filesystem isn't filled with zeros to destroy that data?
I do development for a living and don't require details on how they fixed the issue. 99% of people would not even understand it if they did.Great comment their reply doesn't satisfy me either, its clear that anyone satisfied with this response has never looked at a line of code in their life, no one cares about why the photos returned or where they were stored.
WHY were they not deleted, files that are truly unallocated do not survive as long as apple and other reports have been saying these photos have remained for, are the same storage and deletion systems used by notes or keychain? From the company that has full length whitepapers for security on their site, this bug needs something around that caliber published.
Plenty of people have not “let it pass”.If a Chinese company was involved this discussion would be in a different tone, but because is Apple we just let it pass??
This is the issue that is cumulating in the U.S.If you know anything about data and data deletion then what Apple said is a clear enough answer as to what happened. If you think deleting a file means it's gone from your storage (on any kind of device) then yeah nothing will be satisfactory.
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?That could well be the original error - it deleted the record of the photo from the database, but the final step of deleting the file failed, so the photo vanished from the library until Apple added a cleanup step to 17.5 to find the orphaned files and show them to the user.
I imagine the dev who added the cleanup step thought they were being helpful and people would be grateful to see the 'lost' photos!
Everything is present on the disk until something else overwrites it this is how storage works.This does not explain why certain files were not deleted in the first place, and were still present on the disk!
I wonder what else is present on the disk ?
Zero, when you set up the phone as new it gets new hardware encryption keys, so old data is useless.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?
Or if the database is corrupted and the "deleted" data is backed up and restored to another device. That seems to be one of the concerns here.Everything is present on the disk until something else overwrites it this is how storage works.
But that is also how backups work, it copies everything and then restores everything, it didn't have much bigger issues.Or if the database is corrupted and the "deleted" data is backed up and restored to another device. That seems to be one of the concerns here.