Log in to create and rate content, and to follow, bookmark, and share content with other members. Not a member? Join Now!

AnsweredAssumed Answered

Mac Security - FM-Product not recognized as "identified developer"

Question asked by Benjamin Fehr on Oct 11, 2013
Latest reply on Oct 21, 2013 by codecruncher

Like • Show 0 Likes0
Comment • 11

Summary

Product

FileMaker Pro

Version

12.0.4

Operating system version

Mac OSX 10.9 GM

Description of the issue

Mac OS with security setting "Allow apps … from: Mac App Store and identified developers"
get blocked / can't get installed

Steps to reproduce the problem

set Mac OSX setup for 'Security & Privacy' to setting described above.

Expected result

Filemaker Products as part of the Apple products family get's recognized by Mac OS as product from a 'identified developer'

Workaround

temporary change security settings to install any Filemaker products

No one else has this question

Outcomes

11 Replies

disabled_ntaylor Oct 14, 2013 12:27 PM
Mark Correct
Correct Answer
Benjamin Fehr:

     Thank you for the post.



     Our Testing department had a previous report (not through the Forums) of this issue with Mac OS X 10.9.



     According to Answer ID: 11006, this issue was resolved for Mac OS X 10.8 with the release of FileMaker Server 12.0v2.



Mac OS X Mountain Lion compatibility with FileMaker Server 12 and FileMaker Server 12 Advanced



     Additionally, I added your comments to the previous report.



     TSFalcon

     FileMaker, Inc.
Like • Show 0 Likes0
Actions
Benjamin Fehr Oct 14, 2013 3:33 PM
Mark Correct
Correct Answer
     TSFalcon:

     Please take note that this issue still appears on Mac OSX 10.8 (and 10.9) with FileMaker Pro (Advanced).

     kind regards

     Benjamin
Like • Show 0 Likes0
Actions
philmodjunk Oct 14, 2013 3:34 PM
Mark Correct
Correct Answer
Please also note that the KnownBugsList does a much better job of reporting the discovery of a bug than it does documenting when or if a bug has been fixed by an update. That same database for example, lists a number of FMP 11 and older bugs that were fixed by a release of FIleMaker 12. Few if any of those were reported in any forum post, but most were reported as "closed" due to either my testing of one that interested me or via the generous efforts by an online friend of mine who volunteered to run through some of the older reports from a "mac perspective".

I would love it if more interested parties would select a few old bug reports and then test them to see if they still apply to the current version--letting me know via PM if they seem fixed in the latest release.
Like • Show 0 Likes0
Actions
disabled_ntaylor Oct 14, 2013 4:03 PM
Mark Correct
Correct Answer
Benjamin Fehr:

     Thank you for the reply.



"Please take note that this issue still appears on Mac OSX 10.8"



     To attempt to replicate, I performed the following on an iMac with 10.8.5:



     1. Changed my Gatekeeper settings to match the screenshot above.

     2. Installed the FileMaker Pro 12.0v4 Trial

     3. Installed FileMaker Pro 12.04 Advanced



     Neither installation prompted an unidentified developer message.



     Perhaps, I am missing a step to replicate?



     TSFalcon

     FileMaker, Inc.
Like • Show 0 Likes0
Actions
Benjamin Fehr Oct 14, 2013 4:07 PM
Mark Correct
Correct Answer
     Hi Phil

     again many thanks for that great job you're doing.

     I'll still report wether a bug is resolved or not with every new FM release for those issue's I'm involved.



     kind regards

     Benjamin
Like • Show 0 Likes0
Actions
Fred(CH) Oct 14, 2013 11:23 PM
Mark Correct
Correct Answer
     Hi Folks,

     I know well we are in the "Report An Issue" section, but since it is closely related, i would like to ask you this :

     Is this developer identification supposed to work with the Runtime Solutions ? It would be nice...

     Because Benjamin talked about "Filemaker Products", i can confirm i am experiencing this problematic daily with my Runtime Solutions.

     Bye, Fred
Like • Show 0 Likes0
Actions
Benjamin Fehr Oct 14, 2013 11:07 PM
Mark Correct
Correct Answer
     TSFalcon:

     You performed the same way as I did. I did once with a new iMac with current OS 10.8.x AND with my MacBook running OS 10.9.

     I use FMPA_12.0.1.dmg Installer and later perform the fm_updater_12.0.4.

     Please have included in this report that, as Fred reported, same issue occurs for any FileMaker Runtime solution.
Like • Show 0 Likes0
Actions
disabled_ntaylor Oct 18, 2013 3:56 PM
Mark Correct
Correct Answer
Benjamin Fehr:

     Thank you for the reply.



"I use FMPA_12.0.1.dmg Installer and later perform the fm_updater_12.0.4."



     Use the most up to date FileMaker Pro 12 (Advanced) installer to resolve this issue.



Answer ID: 10984, Error Message: Unidentified developer error when installing FileMaker Pro with Mountain Lion or Lion 10.7.5 states:



Workaround


FileMaker Pro 12 or FileMaker Pro 12 Advanced: Download the latest version of FileMaker Pro 12 or FileMaker Pro 12 Advanced from your FileMaker Store Software Downloads page associated with your order. This updated image file will install correctly, without any Gatekeeper security messages.

Note: Versions downloaded from the FileMaker site prior to 9-June-2012 may require a new download to install.

     OR


          Open the FileMaker Pro 12 or FileMaker Pro 12 Advanced install image and Right-Click (Control click) the FileMaker Pro 12 or FileMaker Pro 12 Advanced.mpkg file and choose "Open."

     Lastly, a FileMaker Runtime solution is an application compiled by the FileMaker Developer. Once the file is compiled into a royalty-free runtime solution, then the developer is no longer FileMaker Inc. nor an Apple "Identified Developer." More information can be found in the help here:



Your responsibilities as a developer (FileMaker Pro Advanced)



     TSFalcon

     FileMaker, Inc.
Like • Show 0 Likes0
Actions
codecruncher Oct 21, 2013 5:19 AM
Mark Correct
Correct Answer



          Is this developer identification supposed to work with the Runtime Solutions ? It would be nice...

          Because Benjamin talked about "Filemaker Products", i can confirm i am experiencing this problematic daily with my Runtime Solutions.

     @ Fred

     Your runtime solution is a new app file that needs to be signed by the creator (which is you). You will have to join the Mac Developer program and apply for your own Mac Developer ID. This will enable you to create certificates which allow you to sign your runtime solutions.
Like • Show 0 Likes0
Actions
Fred(CH) Oct 21, 2013 5:47 AM
Mark Correct
Correct Answer
TSFalcon & CodeCruncher :

     You are right and I can perfectly understand that behavior. It was more a question than a report, as i said initially.

     But i still think my question was relevant. Also because when we install a Runtime Solution OR just a File Solution on a computer, there are numerous same responsibilities by FMI and by the FileMaker developer in both cases. Even if, legally speaking, FMI doesn't have any responsibility in the first case.

     Eitherway, thanks for your answers in particular to CodeCruncher for his consult.

     Bye, Fred
Like • Show 0 Likes0
Actions
codecruncher Oct 21, 2013 8:54 AM
Mark Correct
Correct Answer


     @Fred

     Your pictures shows the info.plist of your runtime which can edited by right clicking on the app icon and selecting show package content. A signed file identifies the creator of the file and not the copyright owner. As soon as you change the original file in any way (which includes editing the info.plist) OS X will invalidate the original FileMaker signature and you will have to sign the file with your own certificate.
Like • Show 0 Likes0
Actions

Mac Security - FM-Product not recognized as "identified developer"

Summary

Product

Version

Operating system version

Description of the issue

Steps to reproduce the problem

Expected result

Workaround

Outcomes

Related Content

Recommended Content