iOS SDK

GoZync can be used to sync files from within packages bound using the FileMaker iOS SDK. This means that you don't have to bind a new package every time you fix a bug or improve your app.

You'll find an overview of how GoZync works with the SDK, and links to the SDK documentation and Todd's posts about the SDK here: In-App Updates for the iOS SDK

While SeedCode can't support the SDK itself, or help bind your files, we can help you configure GoZync to work within an SDK package. This means adding a launcher file to your solution. Here's how:

Using GoZyncLauncher.fmp12 for your native iOS app

Follow these steps to use GoZync's Launcher file for an iOS SDK deployment of your zynced solution. If you're not yet running GoZync 5.08 or higher, see the VersionHistory page to get updated to the latest GoZync build first.

1. Follow normal iOS Application Instructions to generate your app.
2. Create a Custom URL Type. Call it something unique to your application.
3. Place the GoZyncLauncher.fmp12 file into the Solution Files Folder.Delete the PlaceHolder.fmp12 if it is there.
4. Open the configFile.txt and change "launchSolution = PlaceHolder.fmp12" to "launchSolution = GoZyncLauncher.fmp12".

Open the GoZyncLauncher.fmp12 file

5. Edit the Custom Function "URLScheme". Make sure the urlPrefix matches the one you set up in Xcode.
6. On the Settings Layout, populate the two fields that specify your FileMaker Server and the name of your GoZyncHosted file.
7. Modify the "Main Solution" External File Reference. Just change the File Name part to your Main Solution Files name. The launcher will use this file reference to open the first file in your solution. If the files aren't on the device, the Launcher will ask GoZync to install them for you, then launch them.
8. Close the GoZyncLuancher.fmp12 file.

Thats it! You're done!

Build the app to the simulator or a device. It will launch and install the GoZync files and launch them.