I was just identifying in the identify modal and identified this as Dracaena fragrans. I have no idea what would have caused this error from my end (console shows a 500 internal server error but I didn’t have dev tools open when it happened to catch the offending request). Regardless of the server side bug, the identify modal javascript is not parsing the error state correctly obviously. Expected behavior would be for the popup to say “Error: internal server error”.
I see this every so often, but it doesn’t really happen consistently.
i think the issue here is that the server is providing a single error, but the screen is expecting an array of errors to be returned. the screen tries to iterate through an array, but since you just have a string, it instead iterates through the letters of the string: I-n-t-e-r-n-a-l-…
when i was adapting my own pages to handle errors coming out of the v2 API, i noticed that they didn’t always return a consistent structure like v1 did. (v1 was always just a single error, but v2 has variable formats, depending on the type of error.) so the API may just need to be more consistent with the error structures that it uses, or the screen may need to anticipate multiple error formats and be ready to handle them all.
Every now and then you see an error on the error popup. 