Please fill out the following sections to the best of your ability, it will help us investigate bugs if we have this information at the outset. Screenshots are especially helpful, so please provide those if you can.
Platform (Android, iOS, Website):
iOS 18.4.1 iPhone SE App version number, if a mobile app issue (shown under Settings or About):
102 161 Browser, if a website issue (Firefox, Chrome, etc) :
URLs (aka web addresses) of any relevant observations or pages:
Screenshots of what you are seeing (instructions for taking a screenshot on computers and mobile devices: https://www.take-a-screenshot.org/):
Description of problem (please provide a set of steps we can use to replicate the issue, and make as many as you need.):
Step 1:
While identifying observations the device gets remarkably warm with some little sunlight even hot to the point where the screen starts to dim down
Step 2:
Indeed.
Currently I hold back about 200 to 500 observations in the app which are not uploaded to the server (so as to not overwhelm IDer with the sheer amount of obs). From time to time I release batches of up to 50 or so to be uploaded.
Onto that batch of local observations I added a greater number of observation without identifying them in the first place. After the adding was done I started identfying those observations that are still only in the app as part of then about 250. During this identification the phone got realy hot as described above.
Meanwhile I realized that the mere browsing in those offline observation makes the device to get hot to a similar extend.
FWIW I don’t think the app is designed for this kind of use, this seems like a lot of observations to make and to hold back. I don’t know if it’s related to energy use, but I think it does mean the app is storing a lot in its cache. You might consider making fewer observations and/or just uploading them sooner and not leaving so many in reserve.
Thanks. Might be good enough as an explanation.
I also understand, that what I am doing is very special. Sometimes edge cases reveal deeper issues. However, I am also fine, if the topic is closed without further actions.
Just to explain: for me it is a more or less normal situation. Im doing it this way for different reasons. First: I avoid uploading observations in the main observation season during a weekend in my area, and also while there are events like a bio blitz or educational event. This is just, because in my area identifiers including myself are owerwhelmed be the numbers, and many observations don’t get a review because of the numbers.
And also: while I am on a holiday trip I tend to make some 100 to 200 observations per day, that I would not upload until I am back at my accommodation. I then would upload the observations, then go back in the list to identify and then start synchronisation. On reason is that synchonizing slows down the app significantly and tend to fail more often if I deal whith the app during this process.
Like @misumeta I am sometimes on holiday and will make large numbers of observations while out – but usually (e.g. if in Canada) I don’t even have internet at where I’m staying, and thus I need the app to actually hold up to hundreds of observations in the cache at a time, at least if I made the observations through the app. Thus there isn’t really much of a choice I can make, unless the idea is just to not upload much to iNaturalist at all… or perhaps to take photos, notes, and annotations outside the app, which is not my preferred workflow. It’s just a bit odd that the solution to an app issue would be “just don’t use the app that much”.
Side note still related to the topic: Obviously iNaturalist Classic can’t do nearly as much as the new app, but it’s much more responsive in its limited functions, and I’ve never had any problem storing several hundred observations in the old app – while I’ve had all sorts of difficulties with the new app. Between the energy consumption detailed in this thread and the display/interface jerkiness and slowness to appear (that I’ve put in other threads), I’ve lately gone back to iNat Classic for actually taking and uploading photos from my phone, just because it’s so many times faster. Of course I still appreciate the much better (even than the web version) notifications display in the new app… but I also have to check my web-version dashboard for notifications on flags. Right now it’s a bit of a disjointed situation where I can only efficiently use each iNaturalist interface for a single function.