HISE image directory not found (macOS)

[Avián]

@Oli-Ullmann I exactly followed your insctruction and the latest video from @David-Healey about How to compile Hise on MacOS 2026. xcode is building HISE but I got round about 49 warnings on my modules and I think I found out why!
this is showing up for every module! But please trust me guys, I followed your instructions step by step! I just skiped the faust part, but David already said, you can skip this, if you don't need it. Please help me to fix this issues the fastest way. I stuck on this for days...

[David Healey]

@Avián can you show me what you see in the JUCE folder?

[Avián]

@David-Healey this one?

[David Healey]

@Avián yes, are there files in the modules folder?

[Avián]

@David-Healey yes

[David Healey]

@Avián are you using the version of projucer included in the JUCE folder?

[Avián]

@David-Healey yes, and then I draged and dropped the standalone from projects

[Oli Ullmann]

@Avián
I don't use the one from the JUCE folder. Like I wrote I use the one from the projects folder! You don't have to drag and drop anything!

[Avián]

@Oli-Ullmann ok I tried this! Now the modules are loaded, let me try if compiling now works. I'm back in a minute. One more question before I do that: Do I need to delete these 2 if I don't use faust?

[Oli Ullmann]

@Avián
Just do it exactly as I wrote. You don't have to change or delete anything!

[David Healey]

@Oli-Ullmann said in HISE image directory not found (macOS):

wrote I use the one from the projects folder

There is no projucer in that folder, or am i misunderstanding?

[Oli Ullmann]

@David-Healey
Sorry, there a the projucer projects he has to use. (Standalone and Plug-In)

So he just have to double click on the project to open and use it.

[David Healey]

@Oli-Ullmann said in HISE image directory not found (macOS):

have to double click

I think it's better to open projucer and the project manually when you're troubleshooting because if you do have two copies of the source without realising you won't know which copy of Projucer is automatically launching.

[Avián]

@David-Healey @Oli-Ullmann ok, again all these warnings...

[David Healey]

@Avián Warnings are not a problem, you only need to watch for errors.

[Oli Ullmann]

@David-Healey
In that case, you're absolutely right! :-)

But if there's only one HISE version on the computer, I felt that using the projects folder was the least error-prone method...

[Avián]

@David-Healey @Oli-Ullmann ok finally it works! Thank you so much guys! Great work, great support! Have a nice day

[Avián]

@Oli-Ullmann @David-Healey I'm sorry but I'm back with this issue. I could compile/export the standalone, the vst3, the au, I was successful signing them, but my notarization for my installer doesn't work, so I went back a few steps and opened the standalone and vst3 and au and then i saw this:
still an issue with the 2 images....
but in HISE it shows up like it should:
My Images are in the right folder, named correctly everything, I don't get it?
BTW when I close and start HISE my project ALWAYS is losing it's script, I copy paste it, so it's not a big problem, but I think this isn't normal.
And maybe all of these little issues are the reason why the Installer notarization was blocking something. I need help again,....

[David Healey]

@Avián These seem like unrelated issues to the original problem.

Have you enabled the option in project preferences to embed images?

@Avián said in HISE image directory not found (macOS):

BTW when I close and start HISE my project ALWAYS is losing it's script,

Scripts are saved when you click compile.

@Avián said in HISE image directory not found (macOS):

but my notarization for my installer doesn't work

What do you mean by doesn't work? Have you codesigned the installer?

[Avián]

@David-Healey

@David-Healey said in HISE image directory not found (macOS):

Have you enabled the option in project preferences to embed images?

Yes

@David-Healey said in HISE image directory not found (macOS):

Scripts are saved when you click compile.

This always shows up if I close HISE and open my saved project again. HISE is always losing the script and I always need to copy paste it again and compile again. This didn't happen on Windows.

@David-Healey said in HISE image directory not found (macOS):

What do you mean by doesn't work? Have you codesigned the installer?

I signed the Installer, cause I thought codesign is just for signing single files like .app .vst3 and not for.pkg
I codesigned my vst3 and components before and notarized them, it works great but my .app doesn't work. the codesign works but by notarizing the standalone it fails by the same issue, I got later by trying it with the installer, so the standalone has to be the problem (single and as a part of the installer files):
{

"logFormatVersion": 1,

"jobId": "e3733774-a429-4671-9f0b-3a5de89e5544",

"status": "Invalid",

"statusSummary": "Archive contains critical validation errors",

"statusCode": 4000,

"archiveFilename": "macOS-Installer_Plugin_DrumKit_Standalone.pkg",

"uploadDate": "2026-01-25T12:44:36.154Z",

"sha256": "d1c1f509cca7f54f3e5b5d927f6fcc429ea834f65b5fdf5cd5ead6524a4a0fec",

"ticketContents": null,

"issues": [

{

  "severity": "error",

  "code": null,

  "path": "macOS-Installer_Plugin_DrumKit_Standalone.pkg/Payload.pkg Contents/Payload/Applications/myplugin/myplugin.app/Contents/MacOS/myplugin",

  "message": "The signature of the binary is invalid.",

  "docUrl": "https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution/resolving_common_notarization_issues#3087735",

  "architecture": "x86_64"

},

{

  "severity": "error",

  "code": null,

  "path": "macOS-Installer_Plugin_DrumKit_Standalone.pkg/Payload.pkg Contents/Payload/Applications/myplugin/myplugin.app/Contents/MacOS/myplugin",

  "message": "The signature of the binary is invalid.",

  "docUrl": "https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution/resolving_common_notarization_issues#3087735",

  "architecture": "arm64"

},

{

  "severity": "warning",

  "code": null,

  "path": "macOS-Installer_Plugin_DrumKit_Standalone.pkg/Payload.pkg Contents/Payload/Applications/myplugin/myplugin.app/LowEnd.zip",

  "message": "The archive at macOS-Installer_Plugin_DrumKit_Standalone.pkg/Payload.pkg Contents/Payload/Applications/myplugin/myplugin.app/LowEnd.zip could not be unpacked. Any executables contained in the archive will not be notarized.",

  "docUrl": null,

  "architecture": null

}

]

}
I really don't know where this "LowEnd.zip" comes from, maybe this is the problem. My Plugin-Name starts with LowEnd, but the name is much longer?!