When a constraint message is added to the last question in a group, switching the device from mobile portrait to landscape and back to portrait causes the same constraint message to appear for all other questions on that page.
validation message.xlsx (12.3 KB)
Hi @Nayana_Balan,
What version of ODK Collect are you using? I have tried your Form on the latest version and can't reproduce the issue.
The 0s in each field in your screenshot, are you entering those yourself or they are also added automatically?
Also the Form that you shared refers to net_kind field but it is not defined, I am assuming you have shared a subset of your Form. Did you try the shared form at end? Does the issue reproduce?
Version: v2023.4.0
Steps to Reproduce:
-
Enter 0 (zero) in all fields.
-
Tap Next to proceed.
-
Rotate the mobile device to landscape mode.
-
Rotate the device back to portrait mode.
Actual Result:
After switching back to portrait mode, the constraint message is displayed on all questions.
Expected Result:
The constraint message should be displayed only for Question 135, not for all questions.
validation message.xlsx (12.5 KB)
Are you sure that the version is v2023.4.0? The last version of 2023 was v2023.3.1.
Is it possible for you to send in a video recording?
What device are you using? Have you tried the form on another phone model?
I tested this on a Realme Narzo 50A device.
I also checked the API at /version.txt, and the response is as follows:
versions:
-
cc2a6725209c466afef9b5e175052b27f05f5aa3 (v2023.4.0-3-gcc2a672)
-
client: 95326b9ad66ec31c93bdb68c29f8797975d93fd (v2023.4.0)
-
server: 63fdf150e1ed81e3b1059050f7b1ba323931ab24 (v2023.4.0)
I tested this on a Realme Narzo 50A device.
I also checked the API at /version.txt, and the response is as follows:
versions:
-
cc2a6725209c466afef9b5e175052b27f05f5aa3 (v2023.4.0-3-gcc2a672)
-
client: 95326b9ad66ec31c93bdb68c29f8797975d93fd (v2023.4.0)
-
server: 63fdf150e1ed81e3b1059050f7b1ba323931ab24 (v2023.4.0)
what is the version of your Collect?
v2024.3.0-beta.0-263-g5154bcbcae
I was able to reproduce the issue on v2024.3.0 but not on the latest version v2025.3.3. My suggestion would be to download the latest version from the Play Store.
1 Like