Skip links

Transferring a FileMaker Runtime to the Mac App Store.

FileMaker training, courses, coaching

Publish FileMaker Runtime app to the Mac App StoreIn the English-speaking FileMaker Café of Filemakertoday the author kirkrr has presented a method to create a FileMaker Runtime-application in the Apple Mac App Store. This opens up new and powerful ways for FileMaker developers to market their database products. Getting a FileMaker runtime into the App Store is not trivial - there are a number of steps that need to be taken before the application is approved by Apple for the Mac App Store. So far, there is no tool that simplifies the necessary steps for a FileMaker developer. But it is possible, and only with free software. The prerequisite is, of course, registration as an Apple developer, which costs 99 euros or dollars per year.

In order to make a FileMaker Runtime application suitable for the App Store, a few steps must be completed for which a number of tools are required:

  • FileMaker 11 Advanced for creating the runtime app
  • Applescript Editor (included in Mac OS X)
  • Textwrangler (for editing plist files)
  • XCode (free of charge for developers)
  • Icon Composer (included in XCode)
  • Preview (included in Mac OS X)
  • PropEdit (Editor for access rights)
  • Terminal (included in Mac OS X)
  • any graphics program
  • iTunes Connect
  • Apple Developer Account
  • Keychain (included in Mac OS X)
  • iTunes Connect account

Register with Apple as a developer

In order to publish a FileMaker Runtime application in the Mac App Store, you must first register as a developer at the specified annual price. As a registered developer, two security certificates must now be generated - one for the application and one for the installer. The two certificates are installed in the Mac OS X keychain during the process and thus enable the FileMaker Runtime app to be signed.

Creation of a "raw app construct" in AppleScript

In the next step, the author describes how the program file is packed into an .app file and uses AppleScript for this purpose. In the AppleScript editor, only a short Script and saved as an application:

-- Applescript
-- Mac path to a hidden script file in the package.
-- SPECIFY THE PATH AND APP NAME OF THE RUNTIME IN THE FOLLOWING LINE
set hiddenscriptpath to (((path to me) as text) & "Contents:Resources:myapp:My_App.app")
-- Convert Mac path to a POSIX path
set hiddenscriptpath to POSIX path of hiddenscriptpath
-- Quota POSIX path
set qtdhiddenscriptpath to quoted form of hiddenscriptpath
-- execute script file
try
     set command to "open " & qtdhiddenscriptpath
     -- display dialog qtdhiddenscriptpath
     do shell script command
end try

This text must be copied into the AppleScript editor and the path and file name must be adapted (name of the runtime and where it will be located in the package). Then save the AppleScript as a program (e.g. on the desktop). A framework is now available in which the other required components and the runtime app can be inserted.

Creating an icon with a graphics editor

Another requirement for publication in the App Store is a meaningful icon for the application. This can be created with any graphics editor such as Photoshop, Fireworks, graphics converter or PowerPoint and must have a size of 512 x 512 pixels. After completion, it must be saved as an icns file using the Icon Manager from XCode.

Adding the FileMaker runtime and icon to the app file

After the .app file has been created with the Applescript Editor, it is opened by right-clicking and [Show package contents]. The FileMaker runtime application must now be copied to the CONTENTS/RESSOURCES folder. The author points out that the file paths must correspond exactly to the information from the previously created Applescript file. In addition, the previously created icns file must also be copied to this folder as the applet.icns file. In a further step, the created icon is assigned to the created FileMaker Runtime app via the clipboard.

Editing the Info.plist

In the next step, the app file created in the Applescript Editor must be opened with the Textwrangler program. Select the info.plist file on the left-hand side in Textwrangler and replace the content with the following content:

CFBundleIconFile
applet.icns
CFBundleGetInfoString
My Runtime Name Copyright My Developer Name 2011
CFBundleIdentifier
com.kpj2.myruntimename
CFBundleShortVersionString
1.3.0
CFBundleVersion
com.kpj2.myruntimename
LSApplicationCategoryType
public.app-category.productivity
NSHumanReadableCopyright
My Runtime Name Copyright My Developer Name 2011

The structure of this code is relatively simple: The first line contains a key or function between the tag, and the second line contains the assigned value between the tag. CFBundleIconFile must correspond to the name of the icon created.

Attention: The CFBundleShortVersionString must be entered in the form x.x.x.

Setting access rights

The next step is to set the access rights within the app file. This can be done either with the suggested PropEdit app or via the command line. In the command line, the rights are set as follows:

sudo chmod -R a+xr /Users/username/Desktop/My_App.app

The FileMaker runtime requires full access rights (rwxrwxrwx or 777).

With the PropEdit program mentioned above, user rights can also be set conveniently via a user interface.

Code signing (codesign) and package build (productbuild)

Code signing must always be carried out in the last step. In order to be able to carry out the code signing, both certificates must have been installed by Apple in the key ring of the respective Mac. The code signing itself is carried out with the codesign command in the terminal.

codesign -f -s "3rd Party Mac Developer Application: First Name Last Name" /Users/user/Desktop/My_App.app/

Copy the "3rd party Mac Developer Application: First name Last name" from the infobox of the certificate in the keychain.

The "Package Build" process is also carried out first using the terminal and then the key ring.

productbuild --component /Users/benutzer/Desktop/Meine_App.app/ /Applications --sign "3rd Party Mac Developer Installer: First Name Last Name" /Users/benutzer/Desktop/MeineApp.pkg

Copy the "3rd party Mac Developer Installer: first name last name" from the info box of the certificate in the keychain. Any files created during the verification of the installation in the /Library/Receipts folder must then be deleted. Before the next step, place the app file in the recycle bin or on a removable medium that can be ejected.

Testing the installation

This completes all the steps required to prepare a correct installation for publishing a FileMaker Runtime application. With the command

sudo installer -store -pkg /Users/kirkr/Desktop/First_Tasks_First.pkg -target /

the installation can be checked for correctness in the terminal.

The author describes an interesting and basically relatively easy way to publish a FileMaker Runtime application in the Mac App Store. The first runtime applications are already available in the Mac App Store, such as this simple one Cash book based on FileMaker. With this article I would like to offer FileMaker developers a short German-language guide to publishing FileMaker runtimes in the Mac App Store - further details can be found in the English-language Original articlewhere the author regularly posts updates in the form of comments.

NoteThis article only describes a technical way to prepare a FileMaker Runtime solution for publication in the Mac App Store. Whether the app is accepted by Apple for publication depends on other factors.

Leave a comment

Share this page:

ERP software as flexible as your company.
We will be happy to advise you.

Customizable ERP software for Mac, Windows and iOS.

You are here: Publish FileMaker Runtime App in the Apple Mac App Store