I’ve had this happen. For me, it seemed to be coming from uploading a photo that was no longer on my phone that had to be downloaded by my photo storage app. I use Google Photos and will delete photos that are backed up. I tested it out a while ago and had the observation post correctly while the photo was on my phone, but when I deleted the local copy and then went to do the upload, it did the double-post.
As stated above, we need to understand the cause before we can fix it or provide prevention advice.
If you are choosing a photo from Google Photos, and that photo is not on your device, the app should download the photo to your device and the upload that copy. Is that not happening?
It downloads the photo and then uploads it, but something in that process seemed to be causing an issue. I plan on taking some phone photos this weekend, so I’ll test it again to see if it’s still a problem.
As soon as anyone experiences something like this, please send a log file ASAP form the app to firstname.lastname@example.org. The more information we can get about the conditions, the better we can replicate and resolve it.
Yup! I messaged them about it earlier in the year when it started happening to me.
Thanks, now I remember…
unfortunately, too late - users appear unaware of the problem if using their smartphones. Only obvious on the web version afterwards.
I dont think the app crashes. I think that this just happens. Only detecting it because of checking blank observations for the City Nature Challenge. But can confirm it is Android - I have not yet come across any iPhone cases.
and this https://www.inaturalist.org/observations/23956659#activity_comment_2859313 has no photo on the website, but apparently looks OK on the app.
Is flagging these going to help?
I requested users to leave these until the programmers had a look at them, but when can I ask them to fix them?
I’m pretty sure this is something we’ve addressed in the latest beta version of the app. If you’re already a beta tester, check the Google Play Store for an update (version 1.11.22, build 346). If you’re not a beta tester and want to try this out, check out https://play.google.com/apps/testing/org.inaturalist.android. If you test it out, please let us know how it goes. I still can’t replicate this issue and since it doesn’t cause a crash it’s hard to see in our log data, so we won’t know it’s fixed until people who are experiencing the bug tell us it’s fixed.
Thanks! I had not realized there was the option to join the beta program. I have long enjoyed being on the so-called “bleeding edge” out beyond the leading edge, past where programs are stable. Beta is stable compared to alpha or nightly builds. I ran FireFox on nightly builds for years, every morning a new build.
-Photo is still in my gallery, not deleted from my phone.
-I do not remember doing special stuff just imported a geotagged photo into iNaturalist and probably uploaded via 4G.
@optilete it definitely looks like you posted https://www.inaturalist.org/observations/24931067 and https://www.inaturalist.org/observations/24931016 with build 346, but are you absolutely sure you created them with build 346? Given that the “observed on” value is today I suspect you did, just want to confirm.
I think around ‘’’‘vandaag …15:34 CEST’’ I imported a geotagged picture into iNaturalist Android app 1.11.22 (346) and the app automatically sync it with iNaturalist.org and made two observations. The geotagged picture is still on my phone.
If this is the time of upload I probably used wifi of Wikimedia foundation. It was crowded at that time so the connection might be not so well.
I installed the app 1.11.22 (346) at the day of release, so ( and now I understand your question) the observation is created and uploaded with the same version of the app: 1.11.22 (346) .
Same photo today gives no troubles: https://www.inaturalist.org/observations/24984463
I should think that in the morning USA sleeps and processing works fine but in the afternoon USA wakes up disturbs my uploads.
At what time are the ‘‘double postings’’ uploaded and what was the server load at that time?
For me this duplicating bug is combined with another bug: whenever I use a previously taken photo to create an observation, the observation will have two photos: the one I wanted to use and an older photo, which I have previously used to make an observation on iNat. I wonder if anyone else has seen this behavior of iNat picking up old photos?
Anyway, I just sent a more detailed description and a fresh logfile to email@example.com, hope it helps.
I found after I turn off the auto-uploading feature in Android app, this kind of double posting is gone.
However, I haven’t used the app to upload lots of observation for a long time…
I have had this problem regularly when uploading from the android app, particularly when I’m using mobile data to do so (ie not always a consistent connection).
My theory has been that it happens when I momentarily lose connection halfway through uploading an observation.
Probably not telling you anything you don’t know. I will try to send a log file.