Error message when adding new observations to projects in Identify mode

Platform: Website

Browser, if a website issue: Chrome, Edge

URLs (aka web addresses) of any relevant observations or pages: https://www.inaturalist.org/observations/identify

Screenshots of what you are seeing:

Description of problem:

This bug occurs when I attempt to add observations to projects in Identify mode using only my keyboard, without mouse or touchpad.
In Identify mode, on the Annotations tab:

Step 1: Type out part of a project name

Step 2: Use the down arrow to navigate to the project you want to select

Step 3: Click Enter to select that project. The “Observation already added to this project” error message will occur (if you left-click with a mouse or touchpad button, the error does not occur).

This is happening even though I can see that the observation isn’t in the project, and I’m using a &not_in_project= filter.

1 Like

This was happening to me also.
For me, it was not just in Identify mode, but also when adding from the individual observation pages.

I made a new traditional project to collect observations of feral oleander plants, and every observation I tried to add resulted in the “Observation already added” popup.

It does seem to actually add them to the project despite the popup. Perhaps it’s sending two add requests from the action instead of one. The first one adds it, and the second one bounces and gives the popup.

I was able to find a workaround - it seems like adding an observation field requirement stops it from happening (though now I just get the popup to add the field info instead, so I guess it’s the same number of popups, but less annoying?)

Project in question in case it’s helpful:

https://www.inaturalist.org/projects/oleander-invasion

I was just able to add some observations to this project of mine, which has no field requirements. Worked in both Firefox and Chrome.

Is it happening consistently?

OK, I was able to replicate and I made an issue. Only happens if you use the keyboard to add it, which @upupa-epops wrote in his OP here, sorry about that.

1 Like