I though the problem was solved but unfortunately the problem persists. The server does not seem to affect the loading error. I have received loading errors regardless of the server used (mobile phone using 4G, WiFi at work, WiFi at home).
@navis, BTW the loading of the Enketo form also relies on the device’s configuration. Devices with higher-end configurations could load the form more quickly than compared with lower-end configurations (when your survey form is too long).
Yes, the problem seems to appear only from time to time. According to the landing page, we have 92 questions (although in reality we only have 16 questions excluding a few skip logic questions that only pop up depending on how people answer the survey). The form is deployed in four languages.
Might the error have something to do with the fact that the survey has been redeployed various times?
In any case, it appears to be working now. I’m hoping the problem won’t reoccur. Is there anything I can do to reduce the likelihood that this problem will reoccur?
Perhaps this is a silly question, but how do I validate the XLSForm? I just submitted my file through the link you sent. I then click on “preview in browser” and then reach what looks like my survey page… everything looks ok (apart from an image not showing).
However, when I press “validate” it says the form contains “errors”, but all errors have to do with the fact that most fields are “required”. Am I expected to fill out the survey completely to check for any syntax errors?
In order to reduce the number of questions or elements in the survey, would it help to delete the following “text boxes” at the end of my survey in the survey builder? They were automatically created when uploading the XLSForms.
If there are syntax issues in your XLSForm, you will not be able to preview the form (and you will also be getting the errors you should be able to track or check). If there are no syntax issues, you should be able to preview without any issues.
We have 5 questions with constraints. Some of them might be relatively complex, such as:
not(selected(., ‘don_t_know’) and (selected(., ‘sale_of_local_government_owned_land_asse’) or selected(., ‘lease_of_local_government_owned_land_ass’) or selected(., ‘sale_of_development_rights’) or selected(., ‘land_value_taxes’) or selected(., ‘none’) or selected(., ‘other’))) and not(selected(., ‘none’) and (selected(., ‘sale_of_local_government_owned_land_asse’) or selected(., ‘lease_of_local_government_owned_land_ass’) or selected(., ‘sale_of_development_rights’) or selected(., ‘land_value_taxes’) or selected(., ‘don_t_know’) or selected(., ‘other’)))