"The saga" of automatic geopoint update when opening an Survey via URL

Question

First of all, I've done a lot of research in the documentation, forums, etc. and I decided to write this question because the behavior I'm getting from the FieldMaps + Survey123 looks a lot like a BUG that has already been solved (BUG-000127130).

Let's go:

* I have a URL that is built and sent from a point popup via FieldMaps to Survey123, both apps on Android.
* The URL has the following structure: <arcgis-survey123://?itemID=xyzx&action=edit&field:xyzx=2&field:xyzxy=222222&update=true&q:globalID=xyzx&callback=https://fieldmaps.arcgis.app>
* When I enter the Survey123 form (everything is fine, with the feature I need from the globalid, etc), the coordinate that is identified as x and y is coming from the feature (point position) clicked on in FieldMaps.
* If I change the appearance of the geopoint to press-to-locate and the user actually clicks, then the coordinate is updated from the location provider of smartphone (behavior I need)
* I'm sure of the difference between the coordinates because I check via a longitude and latitude note fields that I create to debug.
* I need the user to have the updated coordinate of their position (GNSS/location provider) when they enter the Survey via FieldMaps and not the position of the point in the FieldMaps/Feature, because if I needed this, I would pass it as a URL argument.

The description of the first part of BUG-000127130 is very similar - but no question is using relevant question":

"In the Survey123 for ArcGIS field app, the current location is not automatically returned when the survey is opened using a custom URL"...

I also found something related to this in this thread (Automatic geopoint update when opening an Inbox Survey), but I didn't succeed either.

Am I committing a mistake or is this, in fact, the behavior?

abureaux · Answer

Don't forget to link that idea here so anyone that stumbles across this thread can find it!

ceredajunior_UnB · Answer

Well, instead of a bug, I'll turn it into a new desired feature... 🙂

Anyway, I've already been working on a workaround that involves checking some conditions, including the result of a javascript code that calculates the distance between the planned point and the current point, always "forcing" the user to update their coordinate by "click-to-locate".

It was already working, but if it had this possibility, it would be more convenient for many other applications.

Thank you very much for your attention and I'll add it as an Idea for Survey123.

abureaux · Answer

gotcha.

Hmm... I think you are seeing "normal" behaviour. But I see why its frustrating. As you mentioned, you'd feed the lat-lon manually if you wanted to see that location.

Maybe as a workaround, add a second geopoint as press-to-locate that can override the lat-lon provided by the point. This new geopoint would need to be set to "null", and you'd have to extract the lat-lon form it.