Select to view content in your preferred language

Survey123 form loading in Connect V.3.12.232 but not V.3.13.251

455
1
02-08-2022 05:06 AM
DataOfficer
Regular Contributor

I have a Survey123 form we have been using for a year or two, created in Survey123 Connect. When I now try to load it in the latest version of Survey123 Connect ( V.3.12.232) the application freezes. In comparison, the form loads correctly in Connect  V.3.12.232 on a different PC.

I have tried uninstalling and re-installing Connect V.3.12.232, but the issue persists. 
I can provide the log if useful, but here are the last few lines:

<15>1 2022-02-08T12:57:21Z LAPTOP ArcGISSurvey123Connect 7284 - [AppStudio@11205 category="XFormPositionSourceManager" function="onStatusChanged" filename="XFormPositionSourceManager.qml" line="244"] XFormPositionSourceManager: Position source manager status: 2
<15>1 2022-02-08T12:57:21Z LAPTOP ArcGISSurvey123Connect 7284 - [AppStudio@11205 category="XFormPositionSourceManager" function="onActiveChanged" filename="XFormPositionSourceManager.qml" line="314"] XFormPositionSourceManager: positionSource.active: true
<15>1 2022-02-08T12:57:22Z LAPTOP ArcGISSurvey123Connect 7284 - [AppStudio@11205 category="XFormPreviewMap" function="updateMapType" filename="XFormPreviewMap.qml" line="156"] XFormPreviewMap: updateMapType
<15>1 2022-02-08T12:57:22Z LAPTOP ArcGISSurvey123Connect 7284 - [AppStudio@11205 category="XFormPreviewMap" function="updateMapType" filename="XFormPreviewMap.qml" line="156"] XFormPreviewMap: updateMapType
<12>1 2022-02-08T12:57:22Z LAPTOP ArcGISSurvey123Connect 7284 - [AppStudio@11205 category="default"] Qt Quick Layouts: Polish loop detected. Aborting after two iterations.
<12>1 2022-02-08T12:57:22Z LAPTOP ArcGISSurvey123Connect 7284 - [AppStudio@11205 category="default"] Qt Quick Layouts: Polish loop detected. Aborting after two iterations.

 

 

 



Other forms tested so far appear to be unaffected, suggesting there is something in this form structure specifically that is causing the issue. I am currently working to rebuild the form line by line to see if I can identify any offending logic.

0 Kudos
1 Reply
DataOfficer
Regular Contributor

Update: After some further testing, this appears to be caused where a text field calculation is trying to pull answers from a multiple_select question. E.g. calculation = ${multiple_choice_question}. It could do with further testing, but it looks like whether or not the multiple_select question that the calculation is being made from has a relevant expression with it or not is also causing some of the issues.

0 Kudos