Failed To Submit Error

[Anthony_Mosinski]

I recently published a survey using survey123 connect and I am now trying to test collecting data using a browser and mobile device. In both cases, I receive the following error statement when trying to submit the survey. 

"Failed to submit. Hide details - class org.json.JSONObject cannot be cast to class com.esri.core.geometry.Geometry (org.json.JSONObject and com.esri.core.geometry.Geometry are in unnamed module of loader java.net.URLClassLoader @614ddd49)"

I am not sure what this error means or what is causing it. Any help would be helpful. Thanks

[MarcSmith1]

Some more details from our specific scenario.  We house the data for Survey123 on premise.  We have had a survey running for over a month.  We upgraded to 3.15.  Post upgrade, we receive the error message on the published survey (no changes).  I can create a simple survey, with a single text field with a unique field name and publish it just fine.  When I go to submit an answer to the survey for the single text with a unique field, it fails with the error mention above. 

Here is the JSON Object that is failing.

id":0,"adds":[{"attributes":{"is_appstate_going_to_win":"yes","globalid":"{guidreplaced}"},"geometry":{"spatialReference":{"wkid":4326},"x":0,"y":0}}]}]

[AndrewReynoldsDevon]

We have upgraded the version of connect to 3.15.175 using the version 3.15 of the survey123 in the portal.

Since upgrading to this latest version of connect & then publishing a survey it's broken all of our other surveys. We get the attached error whenever we try & submit a survey for both surveys we've created using the connect XL method or the online designer.

[Anthony_Mosinski]

@AndrewReynoldsDevon and @MarcSmith1 I have not received a solution yet. I am working with Esri Tech Support now to figure it out. I will post the solution once we receive one. 

@IsmaelChivite have you heard anything additional about this issue?

[MarcSmith1]

Hello all - We ended up rolling back the update that was applied last Friday.  Once the update was rolled back, the survey's started working again.

[AndrewReynoldsDevon]

We published a survey with the old version of connect 3.13 .251 however we get the same error as with the new version of connect when we go to submit a survey

[Annie_K]

Updating to indicate that the resolution for this case turned out to be an issue related to the following:

• Field names passed in URL parameters are case sensitive. 

[AndrewReynoldsDevon]

With a test survey I just made sure all the parameters for the URL were lower case, then republished but still get the same error when going to submit a survey

[Annie_K]

Hi Andrew,

Rather than ensuring all parameters are lower case, you will ensure all parameters match the case of your survey question names and the field names in your data. For example (from Ismael's Survey123 Tricks of the Trade: Web Form URL Parameters blog post): 

Question names are case sensitive. You must pass the exact name. For example, in the oak survey, field:commonName=Oak will work, but field:CommonName=Oak will not work.

...?field:commonName=Oak

Similarly, if you're incorporating the URL in a Map Viewer map pop-up, for instance, and you want to pass a value from one of the fields in the map's data table, your URL will need to specify that field using the same case as your field name in the data table. If the field name is "Tree", then the URL will fail if "tree" is used.

Case sensitivity is just one of the requirements that needs to be met when creating your Survey URL to pass parameters. If you find that your case is correct, in every instance, and you are still generating errors on submission, there may be another issue with your URL syntax or survey. If so, please feel free to share more details here for the community and/or contact us by opening a new case so that we may troubleshoot toward a resolution.

Thanks!

[AndrewReynoldsDevon]

Thanks for the above however I've now published the exact same survey to our spare server & it's working fine so I think something must have happened on the server with the issue when we upgraded to 3.15 from 3.13. I have a support call with ESRI so will let that continue.