I’ve been running some tests related to consent forms, where I upload a signature and a photo. When both questions are coerced, I’m getting an error involving the signature and a regular photo.
The system allows me to upload the information normally or submit the form, but when I try to view the data, I can’t access the corresponding signature. The image gets saved or displayed correctly, but the signature or drawing is not stored.
I checked the forum, switched browsers, tested with different phones, and also considered whether it might be an external programming issue. After several long hours, I was able to identify that the problem is caused by the interaction between these two image elements.
Additionally, this same error is now appearing with older consent forms, so I’m not sure if it’s due to a recent update or the server acting up when trying to access the data…
Welcome to the community, @camilo_chiquiza! Would you mind sharing the following information with me through a private message so that I can have a closer look at your case?
Username
Server
Project name
Note: You could share with me a private message as outlined in the post discussed previously:
The issue is caused by a conflict between the photo and signature fields—likely due to both being coerced and handled similarly. The signature (often Base64) may be overwritten, misparsed, or ignored during submission or retrieval. Remove coercion or ensure both fields have distinct keys and handling logic. Check recent updates or backend logs for changes.
