Custom Installer Package blocked by macOS (and maybe Windows 11) - cross posted on Claris Community

Questions
1

I created a “.pkg” file as per Claris instructions for making a Custom install file … but when my client runs it on their computer they get an error:

"FileMaker Pro" is damaged and can't be opened. You should move it to the Trash."

• Note: it DOES install but it is very confusing and it requires the person installing the software to go to Apple -> Settings -> Privacy & Security -> and then find the item that says "FileMaker Pro" was blocked to protect your Mac. and has a button labeled: "Open Anyway"

I need a way to programatically bypass these security steps - I want to do this using device management software, or at least send the installer package to each person ... but not have them have to go through the very confusing (and scary) security steps.

I can not find any information about “signing” the package file (not that I coud do that anyway - I am not an Apple Developer).

Any ideas are welcome.

2

You need to have an Apple Developer account.

Get a code signing certificate within Xcode preferences.

Then use it to sign whatever package you make. Submit it for notarization.

Please google to learn about all the steps or ask your favorite LLM.

Only if the package is properly signed and notarized, the user can install it without annoying security dialogs.

3

Thank you Christian. I will look into the Apple Developer account and the steps to create a signed package file.

My package file did work on my own test computer without any trouble but that computer is running macOS 15.7.3 so I am not sure if it is an OS version issue, or a client computer setup issue.

Notes:
I iwll report back here if/when I have a solution.

The person actually installing the software has years of tech support experience, bit not with Filemaker.

I got on a WebEx with Claris support - they suggested removeing any older version of FileMaker before doing the install and possibly removing a bunch of ~/Library files

• this is doable but is not ideal when installing onto many machines.

Thanks again, Michael

4

If you got to the first level support, I would not expect, that building a package is on their script.

They probably deal with people, that have trouble copying the app from the disk image to the applications folder.

5

Thanks. This person new about the package process, but he indicated that the shell script file from the Claris help site gets updated (often); so I re-downloaded it … but when I unzip it … “Get Info” on the file indicates the file was created and modified in March 2020 (6 years ago). So I am not sure this will help.

I created 2 different PKG installers (one for v22 and one for v21) and they both worked as expected on my MacMini with macOS 15.7.3 It overwrote the existing FMP app without issue (which is what we want). So it could be a Tahoe problem or a problem on the client computer(s).

I am creating a new PKG file but am not expecting it to work.

I will report back. :slight_smile: