Just discovered a problem.
1.Started the download
2.Let it run for about 10 seconds
3.Put fmgo in the background,
4.Waited 15 minutes on the ios desktop
5.Went back to fmgo.
6.It reconnected to the database
7.The script resumed as if the file was extracted but it was not. The file got deleted.
Thanks Mike. Nice document.
Looks like I found some sort of a bug.
If the container field is stored externally, the Export Field Contents function will not resume properly once FMGO regain the focus.
Here's how to recreate the bug.
1.Create a database with a container field and store it externally
2.Create a record and insert a large file in the container (large enough so you have time to hit the home button on your iphone before it finishes ..I tested with a 100 mb file)
3.Create a script that will export the container's Field Contents on the iphone. Add a ShowMessage function at the end of the script.
3.Upload the database to you Filemaker server.
4.Connect to the database using FMGO and run the download script
5.Wait 1-2 seconds and hit the Home button on your iphone
6.Wait 5 minutes or more on the iphone home screen.
7.Go back to fmgo
The script will continue and you will get the message box BUT the file will not be on your iphone.
Now, modify the container field and do not store it externally.
Close filemaker go and retry the same procedure above.
This time it will work properly.
Is this file hosted on FileMaker Server?
It sounds like the external container data aborts if the connection is interrupted. Not really all that surprising. If you consider it a bug, you can report it at https://community.filemaker.com/community/discussions/report-an-issue <https://community.filemaker.com/community/discussions/report-an-issue>. That way, it gets into the tracking system and the development team can have a look at it.
Honestly, though, I’m not sure this is a “bug” per se. I believe the external containers use a streaming protocol based on web technology, which may be incompatible with interrupted connections. Might not be a lot the developers can do about it.
What I find odd (and great at the same time) it's that from my latest tests filemaker go appears to download in the background when the container is not stored externally.
So when you hit the home button while the Export Field Contents has started the download , the script is indeed paused but the Export Field Contents is still downloading in the background ... If anyone could confirm that, that would be great.
I say that because if I start a download process that should take 40 seconds, wait 1 second , hit the home button, wait 5 minutes on the desktop and return to fmgo, the file is already downloaded and the script continues on the line after the Export FC function.
I must say that I don't understand the behavior even though that's exactly what I want FMGO to do
Well I may report it eventually because if the download is indeed continuing in the background when the container is not stored externally , it should do the same IMO with externally stored containers. (see my latest post).