My users have reported that the Survey123 app keep showing the following error message when they try to complete a survey with no GPS signal on their Android devices:
Basicly, what it says in english is : "No position received"
The actual position of the user is not important for our Survey (The user select a location ID). So is there anyway to prevent Survey123 from trying to find the device position?
Will autopopulating the geometry field keep the app from searching for a location?
Thank you for your help.
EDIT: I can confirm the same behavior appear on Survey123 version 3.1.113 on Windows 7. The message appear everywhere in the app. I now see that I can disable it in the App parameters.
Still, is there anyway to disable it completly? I would prefer not to collect personal information about the location of my users when they send me data.
The Survey123 field app will always include a location in a submitted survey, even if the form does not contain a geopoint question. This is because the data is stored in a feature service, and each collected feature must have a geometry. If the user does not want to share their location then they just need to disable the device location sensor - this will result in a null geometry being collected.
You can configure the display of these messages in the 'Alerts' options of the particular location provider settings. By default, the app will display messages and use text to speech announcements to inform you. See here for more details...
The Alert settings do not appear to help the issue. I have all of the alerts turned off, but when you launch the Survey123 field app (testing on Windows 10, app 3.6.153), it still throws an error. Perhaps it controls the alerts while inside a geopoint question in a survey, but the error still comes up on application launch, before opening any surveys.
Is there any way to disable this completely? Due to the presence of this idea, I'm guessing it is not possible at this time?
The error message you are showing is a system error (that concerns location), not a location error (which is affected by the settings mentioned above). The ability to disable that message is being evaluated; for reference, it has been filed as ENH-000124021.