Hi,

Unforntatlely I have tried this (I forgot to mention) and this doesn't fix the issue. I still get the same result.

Hey Adam,

1) I noted you said "it works fine and as intended using a web browser.". Does this mean a PC web browser, or your mobile device web browser?

2) does this only apply to taking photos? or any type of file attachment?

3) When you are logged into the mobile app, can you provide the following versions?

a) Laserfiche Mobile Server

b) Laserfiche Forms Server

c) App version

Thank you and regards,

Andrew

Hi Andrew,

1) I've tried it using the PC Web Browser and it works perfectly. I've tried mobile web browser (just now) and it doesn't even let me press "Submit".

2) It's any attachment. I've tried using an attachment from my iCloud Drive and also from my image library. The same thing happens each time.

3) The version are as follows:

a) Laserfiche Mobile Server: 10.0.0.282

b) Laserfiche Forms Server: 10.0.0.1154

c) App Version: 10.0.0.618

Hello Adam,

thanks for the update. If you upload it via the mobile web browser, and it grays out the submit button, it may mean that the document is still uploading. There should be a progression bar underneath the attachment showing the upload progression.

However on the release mobile app, we did not gray out the submit button. Thus as a result users could submit their form, even though their attachment was still being attached/uploaded. Would you be able to verify that this is not that case for you? and that the attachment is still not loading, when you do press the submit button?

Regards,

Are the Laserfiche Mobile Server and Laserfiche Forms installed on the same machine? We are aware of a problem which surfaced in v10 when the 2 servers are hosted on the same IIS and we are currently working on it. The workaround of using the IP address for Forms server on the Mobile configuration page worked for us so please try again and restart the app so the cookies are cleared. Another workaround would be to type in the Laserfiche Mobile Server IP address in the app instead of the server name and keep the Forms Server FQDN on the configuration page. Basically making sure one is IP address the other is the not. And I guess not hosting the 2 servers on the same machine would work too. If these don't work please open a support case.

Per Adam, the issue still occurs after separating the Mobile Server and Forms Server.

A support case was already created for the issue. We'll update this thread once it is fixed.

This is a bug that user can submit the form before the file upload finishes and an SCR was already filed for it. As a workaround, user can wait for a while and then presses the submit button, to make sure the file is actually uploaded.