WhiteBox Packages Nightmare on Sonoma

[d.healey]

@Lindon It used to look like this

[Lindon]

@ustk said in WhiteBox Packages Nightmare on Sonoma:

@Lindon Oh I reckon we had this issue a while ago... What is your version of Packages?

as I said Im on 1.2.11

[Lindon]

@d-healey then I guess thats just some OS fluff to change the look.. so yes Rhapsody works fine...and installs correctly...

[d.healey]

@Lindon said in WhiteBox Packages Nightmare on Sonoma:

but its refusing to let me build becuse of "permissions"

Do you get an error message?

[ustk]

@Lindon Oh ok dev build... Strange because it was intended to fix this issue. I'm using it on Sonoma with no issue

[Lindon]

@ustk said in WhiteBox Packages Nightmare on Sonoma:

@Lindon Oh ok dev build... Strange because it was intended to fix this issue. I'm using it on Sonoma with no issue

it does fix the presntation tab issue - thats not my problem....

[Lindon]

@d-healey said in WhiteBox Packages Nightmare on Sonoma:

@Lindon said in WhiteBox Packages Nightmare on Sonoma:

but its refusing to let me build becuse of "permissions"

Do you get an error message?

no matter where I tell it to put teh plugin I get this:

[ustk]

@Lindon Sorry, effectively I understand just nothing today...

[d.healey]

@Lindon Have you created in packages previously that work on Sonoma?

[Lindon]

@d-healey nope - "welcome to a new OS and all the pain it brings... best Regards, Apple"....

[d.healey]

@Lindon I mean have you created packages on a previous version of MacOS, that you are able to run on Sonoma?

[Lindon]

@d-healey yes ..its just teh package building thats not working for me...

[d.healey]

Are you testing with one of those projects you were able to build on previous versions?

[DanH]

@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

[Lindon]

@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...

[Lindon]

@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...

[DanH]

@Lindon sure but enable it for login too otherwise I seem to remember it doesn't work after a restart.

[Lindon]

@DanH thanks, sadly now its telling me:

[Lindon]

@Lindon so I guess Im going to have to sign this seperately....

[DanH]

@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.