I’ve observed issues like this also, specifically Enketo is particularly sensitive to geoshapes, more so than KoboCollect. Specifically, KoboCollect will happily permit you to capture and submit self-intersecting polygons; eg
whereas Enketo explicitly checks that none of the polygon edges crosses any others, and will throw an error as soon as you try to edit this (!)
(although I’m not sure exactly what the situation was with your specific example that resulted in a somewhat different error…).
One thing you might try is to make it a geotrace instead of a geoshape (former can overlap itself). But that may not be feasible if, say, you intend to use the area() function to calculate the area of the farm.
Alternatively, if you wish to edit a submission with such a problematic polygon/geoshape, you could resort to performing a bulk edit on it instead, which basically turns off any Enketo validation checks.
