AnsweredAssumed Answered

Plugin conflict with FM12 runtime

Question asked by on May 9, 2012
Latest reply on May 10, 2012 by TSGal

Summary

Plugin conflict with FM12 runtime

Product

FileMaker Pro

Version

FMPA runtime creation

Operating system version

MAC OSX 10.6 and 10.7

Description of the issue

When creating runtime solution with FMPA 12v1 that uses plugins, it seems that plugin calls could conflict with thoose already in /Library/Application Support/FileMaker/Extensions/

Confirmed with a plugin call to Troi Dialog in the runtime solution.

Steps to reproduce the problem

Create a runtime solution with FMPA.
Copy plugins to the runtime solution folders extension folder.
Open the runtime and make a plugin call to a plugin, which also reside in /Library/Application Support/FileMaker/Extensions/

Expected result

Works without any problems

Actual result

Runtime solution crashes

Exact text of any error message(s) that appear

OS X Crash report

Configuration information

This issue has been there in previous versions ( I belive I reported it in FM10v1 )
It got solved in a v2 release of the product.
Seems like the runtime engine include links to /Library/Application Support/FileMaker/Extensions/
and also looks for plugins here. This can give a plugin conflict as it seems that the runtime engine loads both plugins.

Workaround

Delete any plugins on the computer.

You should remove links in the runtime engine to /Library/Application Support/FileMaker/Extensions/
as any plugins that is needed by the runtime solution should be copied and distributed with the runtime.

Outcomes