Duplication of choice question options in Android Survey123 field app

Question

I have created a form using Survey123 Connect (version 3.24.31) and whilst testing the team I built for have noticed duplicated choice question options. I have noticed this is only an issue in the  Android app not iOS. I have contacted Esri support but they have not helped me out. I have had to make a lot of changes and republish the form following testing. I thought perhaps this might have been the cause of the duplicated options but since the duplicated options only appear on android devices and not iOS I believe something else is causing the issue. Initially it was just a choice question within a repeat that was affected now random choice questions throughout the survey are impacted.

Esri support asked me to take a copy and make a change, save and republish and repeat this until one caused the duplication. None of the changes have. They say they can't investigate until I tell them what change is causing the issue. I don't think a specific change is causing the issue as proven by my testing.

Since Esri won't provide any further help I wondered if anybody else has experienced this issue and resolved it.

dougbrowning · Answer

Go into the AGOL item page for the service, then data, then fields, then domains and see if they got double listed there.  It can happen.  Just remove the dups.

Also make sure there are no extra spaces at the end which look like dups but are not.

TylerGraham2 · Answer

Can you share your xlsform?  Are you running the latest versions of connect and 123?  Have you run the analyze tools in Connect?

Try creating a new survey from an advanced or standard template (whatever you used originally).  Copy and Paste, pasting the values only (see image below) to prevent any possible problems from the original xlsform carrying over.

Try making changes to the new survey and see if the problem happens again.  If so, you'll want to let esri know.  They probably won't fix a bug right away, but it may get added to the list for a future update.  If you don't encounter the problem on the new form, have people switch over to using that.