WhiteBox Packages Nightmare on Sonoma
-
@Lindon either move the component etc into a folder on your system drive / folder / library which has all the permissions.
Or.... check Security settings and give Packages full disk access, as well as packages builder, packages dispatcher and packagesbuild...
Then also allow Packages as a Login Item, restart and see if it works
-
@d-healey said in WhiteBox Packages Nightmare on Sonoma:
Are you testing with one of those projects you were able to build on previous versions?
yes...
-
@DanH said in WhiteBox Packages Nightmare on Sonoma:
@Lindon either move the component etc into a folder on your system drive / folder / library which has all the permissions.
Or.... check Security settings and give Packages full disk access, as well as packages builder, packages dispatcher and packagesbuild...
Then also allow Packages as a Login Item, restart and see if it works
OK giving Packages entire disk access worked, thanks Dan...
-
@Lindon sure but enable it for login too otherwise I seem to remember it doesn't work after a restart.
-
@DanH thanks, sadly now its telling me:
-
@Lindon so I guess Im going to have to sign this seperately....
-
@Lindon do you sign with Packages? If so I'm not sure I can help you as I do codesigning / notarising separately in Terminal.
The Dev is quite responsive though so I should email her if super stuck but otherwise just do it in Terminal.
-
@DanH said in WhiteBox Packages Nightmare on Sonoma:
@Lindon do you sign with Packages? If so I'm not sure I can help you as I do codesigning / notarising separately in Terminal.
The Dev is quite responsive though so I should email her if super stuck but otherwise just do it in Terminal.
yep thats what Im going to do - go back to Terminal ..thanks.
-
@Lindon It's most likely another permissions issue. Did you enable everything I suggested? There may be another component I'm unaware of....
-
@Lindon I had this wonderful experience several months ago when I first got my new Mac, mine was a security issue. The two videos I posted at the end of this thread worked for me. :)
https://forum.hise.audio/topic/9178/codesign-error-on-mac-what-am-i-missing/18
-
@HISEnberg said in WhiteBox Packages Nightmare on Sonoma:
@Lindon I had this wonderful experience several months ago when I first got my new Mac, mine was a security issue. The two videos I posted at the end of this thread worked for me. :)
https://forum.hise.audio/topic/9178/codesign-error-on-mac-what-am-i-missing/18
Thanks yeah - my problem is I use WhiteBox Packages so infrequently I have to learn it all again, along with the productsign stuff whenever I use it - and upgrading to Sonoma has only been another hurdle to jump over.. far as I can see....hey ho, well this older product is now back on track(I hope) and I can now rebuild HISE with extended tempos again and get back to the thing Im actually being paid to do...
-
@Lindon said in WhiteBox Packages Nightmare on Sonoma:
my problem is I use WhiteBox Packages so infrequently I have to learn it all again, along with the productsign stuff whenever I use it
You need a script to handle that stuff. Write it once and (mostly) forget about it.
-
@d-healey yeah Im no macos fan/guru so Im not sure where to begin with that...
-
@Lindon Apart from scripts, you can prepare code templates ( .doc, Word files).
Signing, notarization, time stamp...etc all of the codes in a single file per product. You can do it all with a single template, step by step, without any confusion.
These templates are very useful and fast when there are many products or frequent updates are required.
-
@Lindon said in WhiteBox Packages Nightmare on Sonoma:
@d-healey yeah Im no macos fan/guru so Im not sure where to begin with that...
-
@d-healey nice, is this using notarytool?
-
@Lindon said in WhiteBox Packages Nightmare on Sonoma:
nice, is this using notarytool?
Can't remember, it's been a while since I last looked at the video. But if it doesn't let me know and I'll send you my current script which does use it and handles the aax stuff too.
-
@Lindon Are you running the secret "beta"? (Serious question.)
-
@Lindon I had a bunch of silly permissions things recently with Packages. I had to check the "keep owner and group" box to fix it. It lists my computer as the owner and "staff" as group, which I though was strange, but it changes to the end user's account when they install.
-
@clevername27 of Packages? I was sent a Beta by the Dev a few weeks ago after this happened to me. Can PM if needed, but it may well be too old / release version now... 1.2.11