Same in chrome and safari; the network log shows it is returning two separate results for taxon 145300 in the same response, with completely different scores:
"combined_score": 11.555784409149195,
"vision_score": 3.268447145819664,
"frequency_score": 1,
"original_geo_score": 5.280457437038422,
"original_combined_score": 11.555784409149195,
"taxon": {
"id": 145300,
"combined_score": 1.7129294357799478,
"vision_score": 2.348940260708332,
"frequency_score": 1,
"original_geo_score": 1.0891334153711796,
"original_combined_score": 1.7129294357799478,
"taxon": {
"id": 145300,
So I assume it is a backend issue not android or web specific