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
App version number, if a mobile app issue (shown under Settings or About):
1.28.10 (563),
1.28.19 (572)
Browser, if a website issue (Firefox, Chrome, etc) :
URLs (aka web addresses) of any relevant observations or pages:
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:
Open the given observation on the Android app.
Step 2:
The first identification taxon name is displayed as null, while the second is displayed normally. It appears to be null only when there is no common name. It also appears as null elsewhere in the app. It was working normally yesterday but stopped working today. No update was performed in between.
I’ve been having the same issue on the android app today as well, and as you said it seems to show “null” in place of a common name whenever a taxon doesn’t have a common name in the selected language.
+1 On Android app.
1.28.19 (572)
It does not look like a problem, observations are uploaded as normal. When the common name does not exists it shows null.
How to get the react native app on an Android machine?
When i originally uploaded the observation I’m 99% sure it didn’t say null - it was when I saw the identifier activity that I first saw it.
Android
1.28.19
That’s what I see today. My default language is Polish. Some of the names are shown as null, and maybe it’s connected with the fact that a lot of Polish taxon names haven’t been added to the system. Maybe “null” appears instead of a Latin or English name when the Polish one is missing.
That first fix didn’t work for me, but @pleary released a second one and it’s looking pretty good. on my device using version 1.28.10 (563).
Note that the “null” name may be cached in the app for some taxa, so you might need to clear the cache or log out and log back in to really fix things.