iOS App SDK 17 + Swift App Delegate

Document created by Brian Hamm on Jul 11, 2018Last modified by Brian Hamm on Oct 12, 2018
Version 13Show Document
  • View in full screen mode

Note: This no longer works as of Xcode 10. I'll update this post when that situation changes, which will probably arrive in the form of an iOS SDK update from FileMaker.


- - -


This walkthrough, and a bunch of other Data API and Swift stuff now resides at GitHub for anyone who wants to nerd out.

GitHub - starsite/SwiftFM: A Swift 4.2 service class for the FileMaker 17 Data API (and other goodies)


- - -


What You'll Learn

How to build a simple FIAS project in Xcode with a Swift App Delegate.

How to trigger a script from the App Delegate.


What This Post Is /Not/

A tutorial on Xcode

A tutorial on Swift

A tutorial on Terminal



iOS App SDK 17+  // 17.0.2 as of this writing

Xcode 9+         //  9.4.1 as of this writing


Here's What We're Going To Do

Navigate to FIAS directory and create a project

Add a Swift App Delegate class

Edit Bridging-Header.h

Finish the App Delegate class

Build (test)

Navigate to ../DerivedData/../

Get an object reference for our App Delegate using `otool`

Assign object reference in `configFile.txt`

Build and run app

Profit! (lol)




Ok, Let's Make A Project!

In Terminal, cd to your FIAS directory, wherever that is. Mine lives in `/Applications`, so:

> cd /Applications/iOSAppSDKPackage_17.0.2

Create a project. Don't forget the leading dot, and mind your spaces

> ./makeprojdir MyDirectory MyProject com.domain.MyProject

After FIAS returns a prompt, you can open the project with:

> open MyDirectory/MyProject.xcodeproj   // or open it via the Finder




Xcode: Create SwiftAppDel File

In the Project Navigator (left sidebar), right-click on the Custom Application Resources folder and choose `New File`. This will be our Swift App Delegate class. Choose `Swift File`, name it `SwiftAppDel`, and click Create. Xcode will ask you about adding a bridging header. Choose `Create Bridging Header`.


This will drop you off in `SwiftAppDel.swift`. We can't do anything in here yet, we'll come back in a minute.




Edit Bridging-Header.h

Open `MyProject-Bridging-Header.h` from the Project Navigator and add these 2 import statements:

#import "UIKit/UIKit.h"   // bridges NSString, NSDictionary, and bool types from FMX_Exports.h

#import "FMX_Exports.h"   // fias class for queueing/firing scripts, I have no idea why FMI named this 'Exports'

Build the project (Command-B) and watch for errors. You shouldn't have any.




SwiftAppDel Class

Open `SwiftAppDel.swift` from the Project Navigator and build it out like this:

import Foundation   // already present



// type the following (auto-complete is your friend)

class SwiftAppDel: UIResponder, UIApplicationDelegate {


    var window: UIWindow?



    // did finish launching

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {


        print("\n\n*** swift app delegate! \n\n")   // disco!


        return true




    // return foreground active -- this is a FIAS delegate function (not part of UIKit)

    func completedReturnToForegroundActive() {


        print("\n\n*** return foreground active! \n\n")


        // firing a script requires the 'fmurlscript' extended privilege in your .fmp12 file

        FMX_Queue_Script("PlaceHolder.fmp12", "MyScript", FMX_ScriptControl(kFMXT_Resume), nil, nil) 







Build Project (Command-B)

Take care of any errors or typos before proceeding.




Terminal: Navigate To DerivedData/...

DerivedData is where Xcode stores project build data. To get FIAS to 'see' our Swift App Delegate, we need to use a command line tool called `otool`. First, cd to DerivedData/ all-the-way-to / (which is a directory):

> cd ~/Library/Developer/Xcode/DerivedData/MyProject-gznmjbw.../Build/Products/Release-iphoneos/

If you're familiar with Terminal, this can all be done rather quickly using [tab] auto-complete.




Get Object Reference To SwiftAppDel

When you've successfully landed in ``, do this:

> otool -o MyProject

This outputs metadata for the `MyProject` Unix executable inside of ``. Check the output for a reference like `_TtC4MyProject10SwiftAppDel`. Copy this value to the clipboard. Include the leading underscore.




Xcode: Update FIAS Config File

Return to Xcode, open `configFile.txt` from the Project Navigator, and update these settings:

launchSolution           = PlaceHolder.fmp12 (or your solution file)

solution CopyOption      = 1

applicationDelegateClass = _TtC4MyProject10SwiftAppDel



Run (Command-R)

Click the 'Play' button in Xcode (or Command-R) to run the project. Shortly after your app launches you should see a "swift app delegate!" message in the console/debug area. High-five yourself or the person nearest you.


Now press your device Home button and re-launch the app (from the device). This time, completedReturnToForegroundActive() should fire and post a "return foreground active!" message to the console. If you go back and include a 'MyScript' in your solution file (and enable fmurlscript), that will fire as well.




Further Reading

There are lots of app lifecycle (delegate) methods. You can read more about them here:

UIApplicationDelegate - UIKit | Apple Developer Documentation





Happy Coding!




*** Extra Credit ***

Here's a look at the `FMX_Exports.h` Objective-C header, to give you an idea how `FMX_Queue_Script()` works.


My last two `nil` arguments in the Swift example (above) are for a script parameter and a variables dictionary, respectively. The script parameter is typed as String. The dictionary is typed [String: String], instead of the more common [String: Any] you might expect. Also note that the Swift `FMX_Queue_Script()` function signature varies slightly from its Objective-C counterpart. Swift needs to cast `kFMXT_Resume` back to UInt8.


#ifndef FMX_Exports_h

#define FMX_Exports_h


#ifndef _h_Extern_

typedef unsigned char  FMX_ScriptControl;










// FMX_Queue_Script


// Queues script <scriptName> from file <fileName> to be queued to run.

// Parameter scriptParam will be passed to the script as a parameter.  scriptParam may be nil.

// The variables dictionary, if non-nil, supplies one or more local variables with values which

// will be set during execution of the script.

// The user account must have FMURLScript extended privilege. ** emphasis mine **

// Returns true if the script was successfully queued.


extern bool FMX_Queue_Script(NSString *fileName, NSString *scriptName, FMX_ScriptControl control, NSString *scriptParam, NSDictionary<NSString *, NSString *> *variables);


#endif /* FMX_Exports_h */


6 people found this helpful