1 2 Previous Next 24 Replies Latest reply on Jun 13, 2014 11:33 PM by simonclement

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

    simonclement

      Summary

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

      Product

      FileMaker Pro

      Version

      13.0v2

      Operating system version

      OS X 10.9.2

      Description of the issue

      Codesigning of a runtime solution using a developer certificate from Apple does not produce expected result. End users who download and attempt to deploy a signed solution are unable to do so.

      Steps to reproduce the problem

      Obtain a developer certificate from Apple and apply it using the command line to a runtime solution. Deploy the solution and have a user attempt to open the solution.

      Expected result

      That an end user will be able to launch a downloaded copy of the runtime without a problem.

      A FileMaker Pro developer should expect to be able to use the tools that Apple and FileMaker Pro explicitly provide to produce a solution that can be deployed outside the App store without difficulty. At the moment deploying solutions within or outside the App store does not seem to be possible at all.

      This issue has been present for some time and work arounds for previous versions have been found but not apparently for 13.

      General discussion on this issue...

      http://forums.filemaker.com/posts/5ac2e15fae

      A work around for FileMaker Pro 12 that no longer works...

      https://fmdev.filemaker.com/message/129644#129644

      What is causing this issue and why is it taking so long to resolve?

      Actual result

      User receives message that the runtime is damaged and cannot be opened.

      Exact text of any error message(s) that appear

      "xxx is damaged and cannot be opened. You should move it to the trash."

        1 2 Previous Next