Does the "Save a Copy As..." command and/or script step work with a FileMaker file that has been deployed as an iOS SDK app? If so, where is the copy saved?
Yes, it works under the following constraints:
1) You need to choose "self contained copy", it's the only one compatible with FM Go.
2) You need to specify an output file to a FileMaker Go compatible path, like Get(DocumentsPath) or Get(TemporaryPath).
As for accessing the files after creation, you can't access them outside of your original app's filemaker interface since iOS SDK apps do not have a launch center. So you should either email them, or I believe you can re-insert them into a filemaker container field after copying.
Brilliant! Thank you so much for that info, Mike. Cheers. :-)
Sure, without the launch center to view the documents folder it gets a bit confusing, but each app gets its own documents and temporary folders to try and make sure everything works seamlessly. The iOS SDK is pretty brilliant in its own right.
You can also upload the backup copy to Dropbox using the Dropbox API.
The reason we want to be able to save a copy of the file is as a backup in case the original file becomes corrupted and unopenable. In such a case, would the copies that were saved to the SDK app's Documents folder be accessible/recoverable?
That may be a little rough to do, as you'll need to track copies of the files as they are exported and you will need the original file specified in the .plist settings to open and launch into the other copied file.
What you may want to do is build a "launcher" file that tracks the current version and handles launching the "main" file. This way you can reference an external file with a global variable. (EG open $$file, where $$file is set programmatically). Then set your plist to open the launcher file as the default file. I've used this style of configuration to roll out .fmp12 updates to the users without having to vrev the entire app.
Should the launcher file ever become corrupt or inoperable it would cause the need for reinstalling your app, but overall you'd probably have a much lower chance than relying on your main file.
Yes, they would be accessible, but as Mike states it may not be an easy task and I don't recommend using the documents folder because the update process to import data from old database to new databases, counts the number of databases in the documents folder to determine that an update has been done. Such as the update process create by yzysoft if there is more than 1 file in the documents folder then there is an update. Again, that's why I recommend uploading backup to dropbox.
Retrieving data ...