Jump to content
Sign in to follow this  
phofstetter

Plugin does not load on Filemaker Server 18

Recommended Posts

Hello

We updated to Filemaker 18 Server and we are using a Custom PlugIn made by ScriptMaster 5.2.

On the Filemaker Server 18 the PlugIn can not be loaded.

What we need to do for using the PlugIn on MacOs and Windows Server?

 

Kind regards

Philipp

Bildschirmfoto 2019-07-12 um 18.36.51.png

Bildschirmfoto 2019-07-12 um 18.38.49.png

Share this post


Link to post
Share on other sites

Hi phofstetter,

In FileMaker 18, plugins are now required to be signed. Custom plugins generated by ScriptMaster are not signed by 360Works, and will need to be signed by you. Please follow the instructions in our documentation at the following link http://docs.360works.com/index.php/ScriptMaster#FileMaker_18_Changes on how to sign your custom plugin. Make sure to download the unsigned version of ScriptMaster in that documentation link.

Share this post


Link to post
Share on other sites

Hello

I could not understand how to do this. I downloaded Xcode, a 7.7 Gb heavy file but I could not found how to proceed.
The instructions on the link you provided are not clear to me.

Can you please send me a step by step instruction how to do this task?
How to sign a Mac plugin through Xcode?
Can we sign also the windows plugin through this process?

If no, how to do this?

Can you offer a service where we can sign our plugins easily?

I guess that many of the Filemaker developers are struggling here also.

Kind regards
Philipp
 

Share this post


Link to post
Share on other sites

Unfortunately, we do not have a step by step guide for this process. But once you have generated the custom plugin using the unsigned version of ScriptMaster, you can follow the instructions from one of these blog posts on the same topic. Please take a look at the following links. I apologize for this inconvenience, but it is necessary due to the changes made by FileMaker 18.

https://www.troi.com/plug-in-development/code-signing-filemaker-plugins/

http://fmplugins.idma.nz/index.php?title=Code_Signing

Share this post


Link to post
Share on other sites

Hello

We have tried to sign the code using your links on the web but we could not sign it on Mac. For windows we either did not try.

We struggled in setup in XCODE-Beta the right projects. We used «macOS -> Generic Kernel Extension». 
Then we pointed to our existing plugin made with ScriptMaster. We could see the general tab now and the signing&capabilities tab. Here we did the settings.
We then opened the tab Build Phases. We needed to use the +sign and add «New copy file phase». We used in the dropdown «Absolute Path and made the settings. But we struggled in how to set the path under name where we needed to check «Code Sign on Copy»

We then hot the Run Arrow Button and the message «Build Suceeded» open-end.

We could not found the new build plugin nowhere and in Terminal we see the message 
Philipps-MacBook-Pro:Neuer Ordner philipphofstetter$ codesign --verify --verbose=4 fmPROVE.fmplugin
fmPROVE.fmplugin: invalid Info.plist (plist or signature have been modified)
In architecture: x86_64

We are completely in the dark since we are not full fledged programmers. We need your support in order to become that fixed. If you wish we can arrange a Teamvier session where you can come to our system.

Thank you for a feedback and kind regards

Philipp

Bildschirmfoto 2019-07-22 um 15.33.26.png

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.