It’s both an application, but also it contains other code signed libraries, and includes its own separate BaseElements plugin, which also needs to be signed. It’s not an application built with Xcode, so we can’t use any of the native tools. The BaseElements runtime has some unique issues when it comes to all of this.
A lot of this is complicated by the nature of runtimes. This bug isn’t fixed in 18.0.3 as of this writing. Generate a runtime from a brand new file, and it crashes on launch. Mac OS Catalina added another security feature that means that you now also need to notarise your code signed app, by sending it to Apple to verify it before it will load without issues.įinally, in FileMaker Pro 18.0.2 runtimes just plain stopped working. One of the Mac / Safari updates required you to sign your dmg files so that you can drag the app out of the disk image without otherwise authorising it or resorting to workarounds. In Mac OS Sierra there was a new added path randomisation security feature that meant that a non code-signed app would have issues running, so we needed to start signing the runtime to avoid issues. What this has meant in practice is not clear. This doesn’t mean they’re going away, just that they’re no longer supported. In FileMaker 14, FileMaker gave notice that runtimes are a deprecated feature. Over the course of the last 5 versions of FileMaker, things have changed in the runtime world :
Install baseelements plugin mac os for mac#
This means you can download a full application for Mac or Windows which will run separately from your FileMaker Pro application. Every version of BaseElements since the very first release have included an option to download a “runtime” version of the solution.
0 kommentar(er)
