Signing and Packaging A Filemaker Runtime For Distribution

Scripting Forums AppleScript | Mac OS X
#1

I’d like to convert a Filemaker 18 Runtime to a Mac application package.

Is anyone able to point me in the direction of a set of guidelines/video that is less bewildering than this:

Packaging Mac software for distribution

Thanks in advance for any advice.

Regards,

Lar

#2

(1) iOS App SDK

Claris offers a program for developers called “FileMaker Developer Subscription” for about $100 per year.

This developer program includes:

• Claris FileMaker Server Development License
• iOS App SDK

• FileMaker data migration tool

• Solution Upgrade Command Line Tool

• Pre-release software

includes:

The iOS App SDK is an Xcode project that allows you to build an app for iOS by adding a FileMaker Pro database document. It seems to be written in C++/Objective-C internally, but it is also possible to generate a stand-alone app for iOS and code sign (a separate Apple Developer Connection agreement is required).

And since Apple Silicon Macs can run iOS apps on Macs, apps built using the iOS App SDK can be run on Macs.

(2) Claris FileMaker Go

If you don’t mind running on a Mac, you can run FileMaker Pro database documents on your iOS device. Claris FileMaker Go is an execution-only FileMaker Pro that allows you to run FileMaker Pro within the scope of iOS features.

FileMaker Pro apps can be distributed only by distributing FileMaker Pro documents, and can be distributed from any site that allows the sale and distribution of Zip archives.

However, Claris FileMaker Go can’t run on a Mac.

#3

Piyomaru,

Thanks for taking the time to reply to my query.

The programme sounds wonderful.

May I assume, because it is server/web-based, that it is cross-platform?

Regards,

Lar

#4

No. They are limited to iOS and are not cross-platform. It is important to note that it does not work on the web.

Initially, I thought that since you wrote “Mac application package”, it was intended to run on one of the local operating systems.

So, what do you really want to do is run a FileMaker Pro database on a web server (without using a FileMaker Pro database server)?

If it’s a paid product, you can find a few things that convert a FileMaker Pro database to a SQLite database. However, don’t expect that “everything” of a FileMaker Pro database can be converted. Also, it’s not very cheap.

#5

Piyomaru,

Apologies. I misread the FileMaker Developer Subscription spec. I thought it was intended to assist creation of an online solution. My runtimes are desktop apps.

Re-reading your original email, I can’t think where I got the online idea from. Another ‘senior moment’ probably…

Thanks again.

Regards,

Lar

#6

Hello from France Lara
• I’ve done it, but it’s a long and hard way to achieve signing, packaging an notarizing a FMPro runtime !
• First step: you need an Apple Developper account (price depending of your country, (99 € per year in France)) in order to get a valid Developper ID and team ID. Next you must create and download two certificates

  • Apple Developper ID installer
  • Apple Developper ID application
    • You have to install XCode on your Mac and download your developper certificates (in the preferences of XCode) because some apps have to use these certicates.
    • To sign the runtime (and eventually non signed plug-ins), you must use a shell script (to be modified with TextEdit). The best exemple can de found in the exemples documentation of the MBS plug-in (named “Mac Code Signing Runtimes”). You can download a trial of MBS plug-in to get this exemples.
    • If you plan to distribute the app over internet, the FMP runtime.app must be “hardened”, in order to be notarized. The ONLY app that can do this is “AppWrapper 4”. Not free, but works fine.
    • To create the installer package, i use “Packages”: this is a very complete solution to create a signed package. You must absolutely add a post-install shell script to remove extended attributes and change chmod settings for the FMP runtime to avoid security messages.
    WhiteBox - Packages
    • I think that" AppWrapper 4" can create the package file, but i prefer “Packages” because it’s most complete.
    • Finaly, if you plan to distribute your runtime, it must absolutely be “notarized”.
    I use “DMG Canvas 4” to create a .DMG containing the “.pkg” and it builds a signed DMG and sends it to Apple to notarize the DMG and the .pkg
    • I spent dozens oh hours to achieve all this by myself.
    Don’t give up, it can be done !
    Best regards, Ekami.
1 Like
#7

Ekami,

Merci beaucoup for the reply, and the detailed instructions. I tried to work it out for myself after I posted my query, and gave up. I’ll try again using your instructions; they’re much clearer than the Apple guidelines.

Over the past few weeks I turned to what I hoped would be the simpler task of creating an iOS version of my app using the Filemaker SDK. Although the process looks straightforward, I’m having trouble with the notarisation (again!). All of the how to guides mention that if you are likely to have problems it will probably be over notarisation. Why does it have to be this complicated?

I purchased an Apple Developer license and created a couple of certificates, but when I compile my code I keep being told that my certficate fails.

Thanks again.

Regards,

Lar

#8

Hello Lar
I only develop FileMaker solutions for Mac & Windows, because iOS cames with lots of restrictions, so coding the scripts is a hassle and i decided to stop thinking “will this function work with iOS ?”. I use a lot BaseElements and MBS plug-ins for FileMaker, and both are essentially made for desktop, not for iOS.
So i c’ant provide help about iOS SDK compilation and notarization.
On MacOS, Apple has made notarization very complicated for security reasons, but with AppWrapper 4 you can get a “hardened runtime” of your signed app. This may take a few tries, but it works and you can get a “Website version” of your app to replace the one created by FileMaker dev tools. If the app is correctly “harderned”, using DMG Canvas 4 to create a notarized .dmg containing the notarized .pkg is an easy and final step. This is the “normal” way for installing on OSX, and yes, it’s complicated.
On Windows, create an installer for a FMPro runtime is another story, and it can be achieved with free apps, but signing the app is not free.
Regards, ekami.

#9

Bonjour Ekami.

Gone a similar and also long way, but found a clever and very easy way with EasyRuntimeSign.
It’s a free FM-file from Thomas Giesinger and the latest version to date is 3.7.
It guides you through all steps including notarize and signing.
You should find it in one of the many FM-related forums.

Best regards from Denmark
Jan