@Anonymous User - Your recommendations worked for creating the feature layer initially via Connect, but Survey123 is submitting geoshapes with null geometry if the geoshape question is moved to a row lower than a null geopoint after initial publishing.
My first geo question is a geopoint set to null, then I have a repeat with a geopoint in it, then a geoshape that's calculated from the min/max lat/lon values extracted from the repeat.
If I publish the survey with the first geo question being null, I end up with a table and an error message that matches the original poster of this thread. Your recommendation to move the non-null geo question to the top for initial publishing fixes this issue.
If I do a test submission without changing this order of questions, the geometry for my geoshape is stored.
If I move it lower than the null geopoint (and the repeat that contains another geopoint), submission succeeds but the geoshape geometry is null.
If I move it back up to the top of the form, the geometry is included in the submission.
If I move the first null geopoint below the geoshape (and the repeat table), the geometry is once again included in the submission.
I've tried this a few times now, including publishing a new survey multiple times. I also queried the feature layer to make sure it wasn't just an issue with the map viewing visualization. I'm using Connect 3.13.234, fyi.
Pictures:
1. Query on first submission, OID1, before moving the non-null geoshape question at the top of the form.
2 & 3. Query on OID2 & 3 after moving the geoshape below the null geopoint. OID2 is automatically created with my calculation. OID3 was a manually created polygon in the app. (extent_acres is one of my calcs on the geoshape, so you can tell the app is recognizing it)
4. Query on OID4, after moving the null geopoint to the bottom of the form (and under the repeat), making the non-null geoshape the first geo question in the form again. Geometry is included on submission.