HISE Logo Forum
    • Categories
    • Register
    • Login

    is already signed

    Scheduled Pinned Locked Moved General Questions
    5 Posts 2 Posters 272 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • orangeO
      orange
      last edited by orange

      The plugin can be exported (IPP is disabled), but while signing the plugin, I am getting is already signed warning in the Mac terminal.

      When I check the signature, it says invalid signature this time. 😕

      Since the signature is invalid, of course Logic Pro X can't detect the plugin. Has anyone seen this?

      • HISE-develop (today)
      • M1 Max Mac Book Pro
      • Monterey
      • Xcode 13.2.1

      NOTE: Auto-Sign is disabled in the XCode.

      develop Branch / XCode 13.1
      macOS Monterey / M1 Max

      1 Reply Last reply Reply Quote 0
      • orangeO
        orange
        last edited by orange

        Ok, forcing seems to work for VST/VST3/AU for now, but for AAX it definitely won't work.

        I've added --force to the sign code. So the signing code is codesign --force -s ...

        Also, remove signature is working too. codesign --remove-signature /path/to/PluginName

        develop Branch / XCode 13.1
        macOS Monterey / M1 Max

        1 Reply Last reply Reply Quote 1
        • orangeO
          orange
          last edited by orange

          I've just tried a develop branch from 31 October 2021, the exported plugins can be signed successfully. Same system.

          So now I am sure that the latest develop branch have the above code signing issue. Interestingly exported plugins have invalid code signature automatically.

          develop Branch / XCode 13.1
          macOS Monterey / M1 Max

          d.healeyD 1 Reply Last reply Reply Quote 1
          • d.healeyD
            d.healey @orange
            last edited by

            @orange said in is already signed:

            Interestingly exported plugins have invalid code signature automatically.

            I think the error is not clear, basically it thinks some kind of default signature has been applied (maybe it has) but the hardened runtime was not enabled. So you need to resign with hardened runtime, the --force flag enables resigning and --options runtime enables hardened runtime.

            The hardened runtime option was originally disabled in HISE by default, then at some point Christoph enabled it, but recently we found it causes issues when compiling on Intel Macs so it's disabled again in HISE and you have to do it manually.

            If you follow the instructions on KVR it also says to use the --force flag and runtime option.

            Libre Wave - Freedom respecting instruments and effects
            My Patreon - HISE tutorials
            YouTube Channel - Public HISE tutorials

            orangeO 1 Reply Last reply Reply Quote 2
            • orangeO
              orange @d.healey
              last edited by orange

              @d-healey The Hardened Runtime is only for the APP, not for the plugins.
              Also on the KVR, the dedicated suggestion that you've mentioned is for the APP. I am using the same code signing procedure on the KVR.

              So I am not sure that this issue is related to the hardened runtime.

              develop Branch / XCode 13.1
              macOS Monterey / M1 Max

              1 Reply Last reply Reply Quote 0
              • First post
                Last post

              32

              Online

              1.8k

              Users

              11.9k

              Topics

              104.0k

              Posts