What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.
We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.
File Upload widget does not allow selection of camera on Samsung S7 android phoneAsked by ChrisHaslett on October 17, 2016 at 03:19 PM
I recently redesigned a form to use only File Upload widgets due to all the recent difficulties we have been having with the Take Photo widget not loading correctly. However, the File Upload widget does not give the option of selecting camera on a Samsung S7 android phone (only camcorder, voice recorder and documents). This is even with allowable filetype set to jpg, jpeg. Interestingly however the Take Photo widget does allow the user to select the camera as an input device. It was my understanding that the File Upload and Take Photo widgets should have identical actions on a mobile device.
I apologize since I don't have a Samsung S7 android phone to test the issue with. However, I have a Motorola android phone. I tested the file upload field and the "camera" tool is showing as one of the options. I am using Google Chrome for testing. May I know what mobile browser are you using?
Do you have another android phone to test the issue with?
Thanks for your reply. The user was using the default Samsung Internet browser, not Chrome. I had him retry today using both Samsung Internet and Chrome browsers and in both cases it is now allowing him to select camera as an input device for File Upload widget. So in very limited testing it appears to no longer be an issue.
Glad to hear that it is now working properly in both mobile browser. We don't have any similar reports about this so it is probably an isolated case.
If you need further help, let us know. Thank you.