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

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.

     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.

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.

     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

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.

     

          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.

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

     @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.