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): Android
App version number, if a mobile app issue (shown under Settings or About): 1.25.7
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/):
I never encountered this behaviour.
I have set my app to NOT upload automatically; I upload only manually, when I have finished IDing all that I have in the pipeline.
I also never select unknown first.
Iām sorry, but why are you iding from the app? Even on mobile phones itās better to user mobile browsers. Ids take time to upload and in browsr you often need to go forward to get it finally saved, I guess app is no different. Try reinstalling the app, but itās not created to do the id work and maybe itās something with your phone memory if it starts only after a few observations.
I wouldnāt have the patience to try to use the app to identify observations. Is this your standard way of identifying, or do you also use the website?
Iām having trouble with mobile uploads as well. I have it even with single uploads getting hung up, crashing the app, or duplicating the observation (at least on my end). Iām on Android as well.
I deleted one of the āduplicateā observations and it deleted both. Today I deleted a different duplicate, and it worked fine, though it did duplicate by itself.
I think it might be related to a recent update, since I just downloaded that yesterday and tried uploading a few hours later.
I havenāt had any major bugs for a while, so it seems likely.
My iNat version is 1.25.11, not sure about the Android Version 12 is all I can find (software updated yesterday).
Are you aware that you can simply swipe sideways from one observation to the next - i.e. without clicking into and out of each observation? I find it a little more stable that way. The app is not especially well set up for a solid identification session, and I prefer to do it on the website - but I find this helps.
I have the same issues as you. Re: duplicate observations, itās always best to check that they are duplicates, and not the app bugging by showing the same observation twice by clicking on them and checking the ID number under āMetadataā. Itās not a solution, but work-around until the bug is fixed.
I also find I need to clear the app data every now and again, because it just gets bloated and canāt deal with the amount of memory itās using. Only do this after itās finished uploading everything, though.
Then it wasnāt a duplicate, itās a bug of how it just shows observations twice, sometimes one and sometimes many, itās been known for years but canāt be fixed it seems.
I donāt find this reply particularly helpful. If the app nominally allows a user to make identifications, and it begins to fail to do so, that seems like a reasonable thing to make a bug report about.
I also ID from the app (often in short waits like waiting at the bus stop or in line) and for several months this was a fine option. Starting recently I also have experienced this issue where observations donāt load. I have plenty of memory available. Iām running iNat 1.25.7 on Android 12.
I changed the title of the bug report to more accurate reflect the specific bug being reported.
This is a known bug and thereās a fix in the current beta version of the app (1.25.12 - 527). I just made several IDs from the Explore page without issues so I think that fix is working. If you want to try the beta version, join the beta testing program here: https://play.google.com/apps/testing/org.inaturalist.android
And yes, the app is not designed to be oneās main avenue for adding IDs but it should work if you want to add IDs with it.
This bug report is about a specific issue when using the Explore section of the app (although it wasnāt clear in the title). The issue you described is very different, so in cases like that itās best to make a separate bug report or find an existing one that describes the same issue. @fffffffff is correct in that the app will sometimes display the same observation twice - not make two duplicate observations. Best way to fix that for now is to log out of the app and log back in.
I think @tiwaneās answer summarizes it, itās actually easier to use browser on your phone if you want to spend time in unusual place, so my answer doesnāt solve the problem, itās just explaining that thereās a way to make id process easier, Iām not defending bugs, but trying to help, if itās not helpful for you, well, maybe it is for other users who started with app.
I hadnāt thought to check the metadata for suspected āfalse-duplicatesā, thatās a great tip. It did make it confusing that I had 2 types of duplicates, one real and one on the client side only.
Do you clear cache within the app, or just go to āApplicationsā and delete there? I do suspect thereās some issue with memory as well, since I find lots of ways to crash the appā¦
I think I did clear cache through the app and I havenāt been getting the duplication error since.