Skip to main content
SiddheshK09
SiddheshK09
Known Participant
February 13, 2020
Answered

How to make Indesign CC2019 plug-in Catalina OS compatible?

  • February 13, 2020
  • 5 replies
  • 2513 views

Hi All,

          We have compiled plug-ins on MAC OS 10.13.6(macOS High Sierra) for Indesign CC2019 and we distribute this set of plug-ins to our client. But some clients facing issue while using this set of plug-ins on MAc OS 10.15.xx (Catalina).  They all are gtting an error message "xxx.IndesignPlugin cannot be opened because the developer cannot be verified. macOS cannot verify that this app is free from malware." on loading of InDesgin CC2019 application.

For this issue we have found a post on adobe forum. In this post we have found that, we need to Notarized our plug-ins before distributing to client.

We also followed some steps mentioned on apple support site to notarized plug-ins, but no luck. 

Has anyone tried this. If anyone facing same issue and able to successfully notarized indesign plug-in please do let us know.

 

Thanks in advanced.

 

Siddhesh

This topic has been closed for replies.
Correct answer Alo Lohrii

For a quick workaround during development of plugins, you could un-quarantine the file and InDesign should load them correctly, details here https://helpx.adobe.com/in/indesign/kb/indesign-and-macos-catalina.html

sudo xattr -r -d com.apple.quarantine MyCustomPluginName.InDesignPlugin

 

However this manual approach to un-quarantine binaries is not the best solution when distributing your plugin to customers. Instead, a proper notarization of your plugin binaries/installer is required as described here https://helpx.adobe.com/in/indesign/kb/indesign-plugin-notarization.html

5 replies

T
Test Screen Name
Legend
February 21, 2020

The question of whether third party libraries need to be signed is an interesting one. In general they cannot be pre-signed (though this would be useful for authenticity checking) since (as I understand it) most apps require loadable modules to have a matching signature (has to be disabled to load plug-ins!) I sign the third party libraries which I include in the Frameworks of my plug-ins. If you find out any different requirements, I'd like to hear about it.

SiddheshK09
SiddheshK09Author
Known Participant
June 23, 2021

Hi,

I'm using OpenSSl libraries in my project and I have to signed these libraries for mac os Catalina and above versions. Do have any idea about signing process/steps? If yes please do let me know.

 

Thanks in advanced.

 

Siddhesh

T
Test Screen Name
Legend
June 23, 2021

Signing is not enough. You need to notarize, which includes signing but is much more. XCode 10 and above integrate notararizaton into builds. You need a paid-for Apple developer membership.

T
Test Screen Name
Legend
February 19, 2020

(From experience with Acrobat plug-ins, not InDesign plug-ins). Plug-ins need to be notarized. Notatizing is not the same as signing (though it starts with signing).  If you can't notarize a plug-in you may need help from Apple, but note that "stapling" will always fail because there is no recognised executable. The notarization is still valid so long as the computer is online. Read notarization reports in detail, and carefully, it may take weeks to track down all the different things you need to solve.

    M
    Community Expert
    Manan JoshiCommunity Expert
    Community Expert
    February 18, 2020

    Hi  SiddheshK09,

     

    If even copying and pasting the plugin does not make it run then it seems that you would need to codesign it as well, as per the sample given in the link shared by  Alo_Lohrii. You could try signing your plugin and not notarizing it as it should be needed and then see what happens, looking at the error it seems this should work.

     

    -Manan

    -Manan
    Alo Lohrii
    Alo LohriiCorrect answer
    Participating Frequently
    February 19, 2020

    For a quick workaround during development of plugins, you could un-quarantine the file and InDesign should load them correctly, details here https://helpx.adobe.com/in/indesign/kb/indesign-and-macos-catalina.html

    sudo xattr -r -d com.apple.quarantine MyCustomPluginName.InDesignPlugin

     

    However this manual approach to un-quarantine binaries is not the best solution when distributing your plugin to customers. Instead, a proper notarization of your plugin binaries/installer is required as described here https://helpx.adobe.com/in/indesign/kb/indesign-plugin-notarization.html

      SiddheshK09
      SiddheshK09Author
      Known Participant
      February 21, 2020

      Hi Alo_Lohrii,

      Thank for the reply. Now, I'm able to successfully notarized test plug-in using notarization steps mentioned in the above adobe help link. But I have signed my code using xcode 10 instead of command.

      I have one query that, do we need to notarize third party libraries like "openssl", if we used it in our plug-in?

       

      Thanks & Regards,

      Siddhesh

      M
      Community Expert
      Manan JoshiCommunity Expert
      Community Expert
      February 18, 2020

      Hi  Alo_Lohrii,

       

      Just a quick question, as mentioned in the example you shared, will the codesign of the plugin file needed now for Catalina or not?

       

      Since its mentioned in the link that hardened runtime entitlement is enabled in InDesign, then is the codesign command actually needed or not. I know i could verify all this at my end, if you have a answer right away that would save me some time. Just being a bit lazy 🙂

       

      -Manan

      -Manan
      Alo Lohrii
      Alo Lohrii
      Participating Frequently
      February 19, 2020

      @Manan all binaries needs to be code signed first, otherwise the last notarization steps won't accept the package

        Alo Lohrii
        Alo Lohrii
        Participating Frequently
        February 18, 2020

        This guide here should be helpful https://helpx.adobe.com/in/indesign/kb/indesign-plugin-notarization.html

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices