iOS 15 deletes photos saved from Messages, yet another bug!
iOS 15 is once again subject to a disabling bug. When the user saves a photo from Messages and then deletes the conversation, that photo disappears from the gallery during an iCloud backup. The issue is still present in the beta of iOS 15.1, which suggests that Apple has yet to find a solution.
Since its deployment, iOS 15 has a series of bugs. When their iPhone doesn’t show full storage by mistake, users should be careful not to open Spotify or their battery will drain within a few hours. In short, it can be risky to perform the update if you do not want to undergo all the inconveniences that go with it. Especially since we discover almost a different one every day.
The new one is quite vicious, because you may not realize it for a while. Indeed, several Twitter users have noticed that some of their photos have disappeared without warning. On closer inspection, it turns out that all of these images are from the Messages app. In reality, when you delete a conversation, you also delete the photos that were received there.
On the same topic: iOS 15 – only 8.5% of iPhones installed the update, down from iOS 14
Be careful not to delete your Messages holdings on iOS 15
Here is what to do if you want to recreate the bug:
- See you in Messages then save a picture from a conversation
- Open Pictures to check that the image has been saved
- Delete the conversation Messages in which is the image
- Perform a iCloud backup
This last step is essential, because the image remains stored until iCloud has performed a backup backup. On the other hand, once done, the photo will have completely disappeared. So it seems that there is a link between the iCloud gallery and Messages, although it is not yet known which one.
This bug is certainly less serious than a touch screen which suddenly decides to stop working, but it can be a big problem when you inadvertently deletes a conversation containing a valuable photo. We therefore strongly advise you to be careful not to delete anything as long as the problem persists. At present, the bug is still present in the beta of iOS 15.1.