Export tool

[Natan]

Not Sure, But i Guess These 2 Nodes Was Working, Just Fine, With Out Trowing Errors Into The Exporter Tool.

No Matter What Value I Set In The Plugin, As Far As I Use Those 2 Nodes, Errors Comes Up.
@ustk Can You Confirm This Sir, If This Broken Or Something?
Thanks

[d.healey]

@Natan Nothing to do with my app

[ustk]

I’m not home before tomorrow and never used those nodes. I’ll check tomorrow how they behave and export. Although I think Christoph said about the STK they’ve been wrapped quickly so they might have instability. Anyway, any current questions about scriptnode issues should not be taken into account since Christoph is rewriting everything. I personally totally abandoned using it until a more viable version is born and a good advice would be « use it at your own risk ». That is just my opinion as a user though...

[Natan]

@ustk Thank You Sir
The Skew Factor On These Two Nodes Strangly Set To "0"
No Mattet What I Connected Them To A Parametr Or Not, They Show Errors In Exporter Tool.

But They Work In The End Product With No Issues

@d-healey Yeah, EXPORTER TOOL Has No Errors At All ️ i Love IT

[Natan]

@d-healey We Should Call It "Bug Finder" Aswell
Without Your App This Couldn't Be Found
Excellent Job Sir ️️️️️

[Natan]

@ustk Sir Any News On Those 2 Nodes?
Thanks

[LeeC]

@d-healey roughly how long does should the Notarizing step take when using the HISE Exporter. I'm currently in the process of using it to build an installer and it's been spinning for 15 minutes with the prompt:

Notarizing: 1/1 Plugin | Uploading: This could take a while...

[Lindon]

@LeeC depends on the size of your upload and the speed of your tinternety connection..and how snappy the Apple servers are today..

[LeeC]

@d-healey is I'm using Xcode 10.1... Will this work for notorization?

[DanH]

@LeeC Sometimes it fails to build the installer and spins in that state forever. It won't tell you what the issue is but probably an easy fix if there is one. Spaces in the notarization file path aren't allowed, and capital 'L's in the project name on windows would fail as well

[LeeC]

I see an error in the console mentioning that

Packaging/darwin/packages-template.pkgproj no file exists

Does anybody know where I can get a copy of this file?

[d.healey]

@DanH said in Export tool:

@LeeC Spaces in the notarization file path aren't allowed

Just for clarification, spaces are "allowed" but the export tool has a bug with spaces on a Mac. It will be fixed when I do the next round of updates. If you want to see the complete list of known bugs you can check the github issues :)

[d.healey]

@LeeC That file is created internally by the export tool. Do you have a space in your project path?

[LeeC]

@d-healey Yep 2 spaces to be exact!
I'll remove them and retry... thanks

[LeeC]

@d-healey That worked thank you.
Managed to get all the way through to Notorization and saw:

Status Message: Package Approved

It completed and I did see a quick prompt from HISE Exporter saying that 'Notarization failed' but when I check in the 'Darwin' folder in my project folder I see a 'PluginName signed.pkg'.

Is there a quick way to check if this file is indeed Notorized?

Cheers

[d.healey]

@LeeC
https://github.com/davidhealey/hise-exporter/issues/21
https://stackoverflow.com/questions/55074168/how-do-i-verify-that-a-macos-pkg-is-notarized

[LeeC]

@d-healey Perfect and apologies for not checking the bug board
Man, I have to say that this is an insanely useful tool and you've solved a very sticky pain point for a lot of us.
Just EPIC!
Thanks again

[SteveRiggs]

@d-healey

I'm having a bit of trouble with getting a signed and notarized installer to work on Mac High Sierra.

I've successfully built an un-signed and un-notarized installer, but when I try notarized one I keep getting this error?

I left it for 3 hours last night and then tried another 2 attempts at over an hour each but the circle keeps spinning.

I made sure there are no spaces or capital L's in the file path or project name but still no joy.

Also made my 2 certificates and put them in keychain. Any idea what could be wrong?

These are the 2 certificates I made...

[d.healey]

@SteveRiggs Any spaces in your project path?

[SteveRiggs]

@d-healey Not that I can spot. Are there any other characters in the file path that could be affecting it?