Reverse Geocode stopped working in public web app survey.

[durus5995]

Hello I have a public survey where the address, city, zip code, and county fields were reverse geocoded from the geopoint question.  The reverse geocoding works in the preview and in the Survey123 fieldapp but it stopped working in the web app.  I did do some tweaking to some of the labels the other day and updated the survey and that is when I noticed the reverse geocoding stopped working.  The survey was published in survey123 connect 3.16 and I have included the XML file that I have from when it was working.  I would appreciate any help or suggestions the community might have.  Thanks for your time.

[IsmaelChivite]

I published your XLSForm using Survey123 Connect version 3.17. Everything worked fine in both the Survey123 Connect preview as well as in the web browser. I do not see why this same XLSForm would fail with previous versions or have an inconsistent behavior across different clients. The XLSForm syntax looks good.  I can't think of anything obvious that would cause a problem.

For consistency, try publishing with version 3.17 of Survey123 Connect, if not already, but again, your XLSForm looks good. I wonder if the problem relates to the sharing of the geocode service: What if someone made the geocode service in your organization private? Assuming you are not logged-in in your browser, this could explain why reverse geocode info does not come when you use the web app.

[durus5995]

Thank you for the response and verifying that the syntax was valid. I was going crazy trying to figure out what was going on. I am unaware of where the geocode service settings are located.  Is it on the feature service itself or is it at the organizational level somewhere?

[SteveE]

Did you ever solve this issue? I am experiencing a very similar issue. Browser geocoding JSON response is empty, works correctly in the app or in Connect however.