is there a particular reason you’ve decided to rule it out?
I associate it very much with attempting to save large numbers of observations without uploading; other users have found similar results. have staff tried making hundreds of observations (with multiple photos that require cache space, not blank test records) to examine this?
on the other hand, maybe staff won’t test that scenario if there’s no interest in planning for it? perhaps this is more a matter of not prioritizing speed/efficiency in the development of the new app. the response to one of the previous threads about a similar issue was essentially “just don’t save lots of observations” to keep it working* —
*that’s at least how I interpret being told “the app isn’t built” for my usual workflow in iNaturalist Classic.
if staff simply do not plan to work on this side of things, I and other frequent observers obviously can’t force them to do so. if that’s true, though, I would like it very much if the more uploading-functional iNaturalist Classic could remain active indefinitely even if it receives no further updates. I don’t know whether it’s simple enough to allow the old app to continue to interface with iNaturalist but I really struggle with the new one and its slow march toward its interface freezing when in between deletion-redownload cycles.