Finalising plugins ready for release



  • Hi all,

    It's been a while! Hope you're all doing good.

    I finally got my Apple Dev licence sorted and am ready to start finalising my first plugins ready for release.

    I'm just wondering, which way around do I have to do things with the Apple dev licence, JUCE Licence and of course the HISE licence?

    I don't fully know how the serial number system works for adding those into the final plugins yet, or also if there is any code that needs to be added first from JUCE and HISE licences before notarising with Apple (to get rid of splash screens etc) I'm a little stuck at the moment as to what I need to do next and in what order.

    I've done some googling and looking around on the forum but not spotted anything that covers the process start to finish.

    For making installers, I have packages installed already for Mac, and I have inno setup installed for Windows, but I've not made much sense of inno setup yet.

    Thanks for any help or links anyway. Any pointers would be mega helpful on the order that I need to do everything in, so that I don't totally nause it up! 😂 I'll do some more research in the meantime...

    (..and I almost forgot... I'm still on Xcode 8 at the moment on Mac High Sierra. I assume I need to get rid of that now and get Xcode 10? Does that even work on High Sierra and am I able to notarise using High Sierra? It's version 10.13.5)



  • @SteveRiggs said in Finalising plugins ready for release:

    Hi all,

    It's been a while! Hope you're all doing good.

    I finally got my Apple Dev licence sorted and am ready to start finalising my first plugins ready for release.

    I'm just wondering, which way around do I have to do things with the Apple dev licence, JUCE Licence and of course the HISE licence?

    I don't fully know how the serial number system works for adding those into the final plugins yet, or also if there is any code that needs to be added first from JUCE and HISE licences before notarising with Apple (to get rid of splash screens etc) I'm a little stuck at the moment as to what I need to do next and in what order.

    I've done some googling and looking around on the forum but not spotted anything that covers the process start to finish.

    For making installers, I have packages installed already for Mac, and I have inno setup installed for Windows, but I've not made much sense of inno setup yet.

    Thanks for any help or links anyway. Any pointers would be mega helpful on the order that I need to do everything in, so that I don't totally nause it up! 😂 I'll do some more research in the meantime...

    (..and I almost forgot... I'm still on Xcode 8 at the moment on Mac High Sierra. I assume I need to get rid of that now and get Xcode 10? Does that even work on High Sierra and am I able to notarise using High Sierra? It's version 10.13.5)

    OK so my experience:

    1. You will need A HISE license, a JUCE license and an Apple Developer ID - any order.

    on a Mac....(not covering AAX here..)

    if you want to have a stand-alone version of your product, and if it needs an icon of its own you need to put the icon in the images folder and call it icon.png (I think that right..) - you cant add it later post compile...well you can but your codesigning wont work...

    1. Compile your plug-in/stand-alone

    2. codesign all your products...VSTs, AUs and Stand-alone (theres pointers on here to the KVR forum that covers it)

    3. Notorize your stand-alone

    4. Build your pkg

    5. Noterize your package.

    6. Staple your package



  • @Lindon

    Thanks mate. It's starting to make more sense now.

    I've had a read and found how to codesign and notarize (I think!) so I will get my JUCE licence started, and speak to Christoph again about getting my HISE licence and it should be ready to roll!

    Do I need to get Xcode 10 first? I'm still on 8 at the moment. I don't want to remove 8 if 10 doesn't work on High Sierra? (or if I don't need it to sign or notarize)



  • @SteveRiggs said in Finalising plugins ready for release:

    @Lindon

    Thanks mate. It's starting to make more sense now.

    I've had a read and found how to codesign and notarize (I think!) so I will get my JUCE licence started, and speak to Christoph again about getting my HISE licence and it should be ready to roll!

    Do I need to get Xcode 10 first? I'm still on 8 at the moment. I don't want to remove 8 if 10 doesn't work on High Sierra? (or if I don't need it to sign or notarize)

    well Im on High Sierra with XCode 10 (I think) so you should be good there..)



  • @Lindon

    After 2 hours of downloading Xcode 10, the inevitable happens 😞 I'm a bit stuck now as I can't upgrade my OS at the moment. Any suggestions?

    Screen Shot 2020-07-14 at 22.30.56.png



  • @SteveRiggs perhaps upgrade to 10.13.6 ?



  • Use XCode 8, don't bother about notarization and if you got a user with Catalina, tell him to right-click and press Open in the Context menu to bypass that junk.

    That's what I do 🙂



  • @Christoph-Hart

    As if it's that easy! 😂 I just had a Catalina user test a beta installer for me and he had no problems doing it like that. Thanks man.

    The only thing I'm wondering now though with having un-notarized or un-signed code... when I send my plugins to other online shops to sell on there and it goes through their testing process, it might sway the decision to them not having them if they are not properly notarized. Have you had any experience with this?

    I would much prefer to somehow get them notarized and signed so there are no problems down the line, but do you think its worth releasing them without?



  • @Lindon

    @SteveRiggs said in Finalising plugins ready for release:

    After 2 hours of downloading Xcode 10, the inevitable happens I'm a bit stuck now as I can't upgrade my OS at the moment. Any suggestions?

    Genius mate. Why didn't I think of that lol 🤣

    I'd love to, but with my Mac refusing to update and just black screening on restart getting stuck there making updating impossible... now I'm stuck on High Sierra 10.13.5 when I need 10.13.6 to run Xcode 10.


Log in to reply
 

7
Online

703
Users

2.8k
Topics

23.7k
Posts