Clear photo cache when iCloud Photos optimization is enabled
I started using iCloud Photos recently and love it. I have photos syncing on my iPhone(16gb), my MacBook Pro(240gb), and in the cloud of course.
My issue is that I have 12 photos on my phone that are not syncing to the cloud. I am on WiFi, the phone is fully charged, and they are just stuck on my phone. I've looked on my MBP and they aren't there. I've looked on the iCloud via the web app and they aren't there.
When I go on my phone to iCloud / Photos, the message says "Low Disk Space - Uploading 12 Photos" I have 163mb of free space on my phone, and 125gb of free space in iCloud.
My Question is, is there a way that I can manually clear the cache of photos that have downloaded to my phone. I have 750mb used in the "Photos & Camera" application, and I am sure a good chunk of that is from me browsing old photos which are temporarily downloaded to the phone for viewing. When I typically look at my library on my phone, the photos start off as empty white squares and that's okay. I've looked at a bunch, and it downloads thumbnails and lower res images of the files. Can I clear these caches to free up some space?
Also, I've read that the system requires at least 300mb of free space on your phone to upload photos to the cloud. Is this true? I can't see why this would be a requirement.
Solution 1:
Apple doesn't list a required/minimum free space, so you'd need to work with Apple support to get that sorted. As for the cache, you've already done all you can.
iOS has several low storage warnings it sends to each and every app to clean up cached files and with < 500 MB of free space, I'd wager you've exercised those limits continuously and it's surprising to me if this is the only thing that is broken on your device right now.
I would:
- Delete one or two large apps that you know the data is safe/unimportant. Try to get 2 GB of free space if you can but 1 GB of free storage should be sufficient.
- Power off the device and power it on to let system cache files re-generate
- Open photos on the device and on iCloud and see if normal operations resume. I've had good luck with photo libraries coming back from all sorts of intentional abuse like you've unintentionally performed. It can take 24 hours or more (if you hit any upload limits) for the cleanup script(s) to trigger so you might wait 48 hours to see if the added space lets iOS complete the upload work that is queued.
Also, Apple does offer debugging profiles for iOS cloud sync if you call in for support and if their "cookbook" method doesn't yield results. If your case get escalated to engineering specific error messages contained in the debug logs can often assist you in further diagnosing why all the photos are not syncing.
You could also just push the photos to a computer or other iOS device using AirDrop or USB and upload them to the cloud from another device and then remove iCloud Photos temporarily from your iPhone to allow enough space to resume normal operations and then re-enable the library with the option to reduce file size.
Basically, the system is designed to stop working when there isn't enough space for temporary files to work. This is the same design as OS X and other unix in general.
These operating systems use free storage space to cache things and make your experience better by accelerating slow resources like network and CPU by saving work when it's done to reuse it later. When you deprive the system of that buffer, things slow and eventually stop.
Solution 2:
The "one weird trick" that works regularly for me is to attempt to rent a large movie in iTunes. Go find a movie that you know won't fit on your phone. Before actually charging you for the movie iTunes will attempt to free up enough disk space to download it.
You can actually try this several times. Some times it doesn't work at all, but often times it will free up a few hundred MB and then you can immediately try again and free up a few hundred more. Each time iTunes will fail to rent the movie due to low disk space, but it will still have cleared a lot of cache in the process.