AnsweredAssumed Answered

Codesigning of FM13 generated runtimes still fails on Mac OS X 10.9 Mavericks

Question asked by intex on Dec 21, 2013
Latest reply on Dec 23, 2013 by TSGal

Summary

Codesigning of FM13 generated runtimes still fails on Mac OS X 10.9 Mavericks

Product

FileMaker Pro

Version

13

Operating system version

OS X 10.9.1

Description of the issue

once again

after codesigning on FM12v5 runtimes failed on Mavericks, it fails with FM13 too.


how should we build apps based on the runtime, if we can´t sign them ?

I posted a bug regarding 12v5, why didn´t they change anything for 13 ?

Is it so difficult to build the components in a way, that they can be signed successfully ?

I have already asked Sam Rowland from Ohanaware again, if he can help with his AppWrapper. But I really have no understanding, why FM can´t solve the problem on its own.

Just realized that these

FMStrs.dls

files are still protected in the generated runtimes. Another bug I posted already years ago - tata, still there :-(

Steps to reproduce the problem

try to codesign a runtime

Expected result

a codesigned runtime app ready for Gatekeeper

Actual result

none, only an error message

Exact text of any error message(s) that appear

test.app bundle format unrecognized, invalid or unsuitable
In subcomponent test.app/Contents/Frameworks/DBEngine.framework

Workaround

none

fail.png

Outcomes