This is the most logical way in bulk processing, why should you import from iNaturalist?
You can combine and split in a iNaturalist batch and delete photos /prevent from uploading
Thanks for your patience. Version 1.1.0 is now live in the App Store, and it includes a fix that will prevent this from happening in the future. Basically, if you were sharing a photo from Photos to iNaturalist, iNaturalist saved a full-sized version of the photo and never cleared it from the app. Thus, the app’s’ size could grow quite rapidly if you shared a lot of photos to iNaturalist.
Moving forward, the app will now clear the photos you share to iNat, but you will need to log out and log back in to clear the cache one last time.
Thank yoiu i have 1.0.27 so i wait a bit (hmm 1.025 is gone???)
As i do not know the password i do not like the refresh option but till now not too much problems with it
To confirm that it helped:
At this point in time I have 550(!) observations unsynchronized in my app backlog, way more than I ever had. Most of the observations include more than one picture. I guess the observations contain more than thousand photos. The app consumes 17GB and still runs with normal speed.
If you can upload a good chunk of them and then check storage again, that would be helpful.
With now 410 Observations left storage went down below 16GB
With a bit up and down I had
18 GB with 381 observations in the app backlog
And
17 GB as I reached zero observations in my backlog.
It doesn’t seem to be a breakthrough.
To compare: iNat classic is at 233 MB = 0.2 GB (!).