Ok
I may have screwed things up a little bit. I am in the proces of moving from LR to Photomator. I purchased the lifetime license and have the app both on my phone and ipad as well.
Everything works great but for one or other stupid reason I looked at my icloud usage and saw Pixelmator was using 1.4gb and the 20 odd files I saw there I could not find in my photos. I thought it may be old photos when I once played around with pixelmator and went ahead and deleted them.
Since then I get the message as per the title every time I do an edit and click the 'done' button. This is only on the phone and ipad app. The one on the mac works fine.
I got a workaround by changing edits to save to the device and not icloud but that is obviously not what I want.
I did try to delete and reinstall the apps but no joy.
Any help would be appreciated.
We have some important news to share: the Pixelmator Team plans to join Apple. If you need product support please contact us here.
Learn moreUnable to save image (Error code: 513)
The Pixelmator Community has been archived and cannot accept new posts or comments.
2024-06-03 04:50:25
2024-06-04 04:49:10
And so the plot thickened. I logged a ticket and it was suggested I edit a file and then turn saving off from icloud to saving it on the device. Next step was to delete the app and reinstall it after which I should switch back to icloud saving.
Tried it on both my phone and ipad but now Photomator tells me icloud is unavailable and I cant toggle the switch.
As a new user trying to move from LR to Photomator this 'bug' so early in my adoption is concerning.
Tried it on both my phone and ipad but now Photomator tells me icloud is unavailable and I cant toggle the switch.
As a new user trying to move from LR to Photomator this 'bug' so early in my adoption is concerning.
2024-06-04 05:18:40
OK, after further investigation it seems like edits I do on any of my devices do 'transfer' to the other devices even though they do say 'icloud is unavailable'.
Strange behaviour but it does seem to work like it should.
Strange behaviour but it does seem to work like it should.