Skip to content
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

Finalizing a form with an attachment which is too big to be sent #6457

Open
dbemke opened this issue Oct 16, 2024 · 1 comment
Open

Finalizing a form with an attachment which is too big to be sent #6457

dbemke opened this issue Oct 16, 2024 · 1 comment

Comments

@dbemke
Copy link

dbemke commented Oct 16, 2024

ODK Collect version

the store version 2024.2.4, the master version e828193

Android version

10, 14

Device used

Redmi 9T, Pixel 7a

Problem description

If a user finalizes a form containing an attachment which is too big (larger than the server's "max file size") to be sent to the server, the user can’t delete the form.

Steps to reproduce the problem

  1. Go to the form and attach a file which is too big to send to the server (e.g. in image widget world 108MB from https://drive.google.com/drive/u/1/folders/1IeuxQZU8Sw90PAOnTRlMToB3Wp_LuCoN.
    trees_registration_new_media.xlsx.txt

  2. Send the form.

Expected behavior

The user shouldn't be able to finalize a form with an attachment which is too big. The attachment should be verified before finalizing the form.

@karntrehan
Copy link

What should be the limit of the attachment size? Is this a config that can come from the server or should we have a configuration at the app side? This too seem to be a good first issue.

@seadowg seadowg changed the title Finalizing an entity form with an attachment which is too big to be sent Finalizing a form with an attachment which is too big to be sent Oct 22, 2024
@seadowg seadowg added this to the Later milestone Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: not ready
Development

No branches or pull requests

3 participants