-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A form is finalized (not sent) if there is "default" auto send setting in the form #6203
Comments
The same issue occurs in a form in which auto send is set to "1". |
@dbemke it makes sense that we'd send the form in this scenario (we shouldn't treat "default" as "false"), but what happens in older versions when I disable auto send at a settings level with that form? Does it send because it treats "default" (or the "1" in the other example) as "true"? |
In the store version in form settings auto send:
Currently default - send button at the end page, the form isn't sent automatically |
What about if auto send is disabled in Collect? In those cases "default" is behaving like there's no |
If in Collect settings there is auto send set to "off" then with default in form settings the form is finalized (in the store version) |
Cool! So with |
ODK Collect version
the master version fb11c14
Android version
10, 14
Device used
Redmi 9T, Pixel 7a
Problem description
A form is finalized (appears in "Ready to send”- isn’t sent automatically) if in the form settings there is "default” in auto send options.
(The issue doesn’t occur in the store version 2024.1.3)
Steps to reproduce the problem
AutoSendDefault.xlsx.txt
Expected behavior
I couldn’t find information in the documentation about using "default” in auto send setting in a form but in the past the setting sent the form.
The text was updated successfully, but these errors were encountered: