HISE crashes when loading my project

[David Healey]

@Oli-Ullmann said in HISE crashes when loading my project:

6de7c97 is the commit since which it no longer works.

Aha got it, I misunderstood. Yeah sounds like the same issue Dan had.

[Oli Ullmann]

@David-Healey
Okay, I feel like a newbie! But I can't get HISE configured.

1. I deleted all HISE app data (from the Application Support folder).
2. I compiled HISE from the source code.
3. I set the HISE path in the settings.
4. I open the Export Setup Wizard.
5. The first 4 checkboxes are checked. However, the “Projucer Works” checkbox is not checked.

This means that I cannot compile networks or plug-ins.

Do I need to do anything differently or keep anything in mind with the new HISE version? Did you have this problem too, @DanH ?

[DanH]

@Oli-Ullmann no! Can you run Projucer normally? I'm using Github desktop to pull in new commits rather than downloading a new Hise each time

[Christoph Hart]

The export wizard is broken - it still looks at the old location so you cannot get past it at the moment. David already mentioned this but good reminder to fix that asap.

You can easily skip it by setting the "Export Setup" flag to 1 in the HISE settings for now.

[David Healey]

@Christoph-Hart I made a PR a couple of days ago https://github.com/christophhart/HISE/pull/853

[Christoph Hart]

@David-Healey ah noice thanks!

[Oli Ullmann]

@Christoph-Hart
@David-Healey
Okay, I clicked “Skip Wizard” in the Export Wizard. I hope that was the right thing to do. Now I'm trying to compile a very simple project. It only contains a sine wave generator. Unfortunately, I get the following error message:

Last login: Tue Jan 20 09:28:33 on console
/Users/mou/Documents/HISE\ Projects/test1/Binaries/batchCompileOSX ; exit;      
mou@Marks-Mac-Pro ~ % /Users/mou/Documents/HISE\ Projects/test1/Binaries/batchCompileOSX ; exit;
Re-saving file: /Users/mou/Documents/HISE Projects/test1/Binaries/AutogeneratedProject.jucer
Finished saving: Visual Studio 2017
Finished saving: Xcode (macOS)
Finished saving: Xcode (iOS)
Finished saving: Linux Makefile
Compiling Instrument plugin test1 ...

----- xcbeautify -----
Version: 2.28.0
----------------------

2026-01-20 09:35:39.811 xcodebuild[1137:17660] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
2026-01-20 09:35:40.813 xcodebuild[1137:17660] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 874. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
2026-01-20 09:35:40.814 xcodebuild[1137:17660] Error Domain=NSCocoaErrorDomain Code=3840 "JSON text did not start with array or object and option to allow fragments not set. around line 1, column 0." UserInfo={NSDebugDescription=JSON text did not start with array or object and option to allow fragments not set. around line 1, column 0., NSJSONSerializationErrorIndex=0}
2026-01-20 09:35:40.816 xcodebuild[1137:17660] Writing error result bundle to /var/folders/qx/0_mrj8z91hd2gj5y61xxknvw0000gn/T/ResultBundle_2026-20-01_09-35-0040.xcresult
xcodebuild: error: Unable to read project 'test1.xcodeproj' from folder '/Users/mou/Documents/HISE Projects/test1/Binaries/Builds/MacOSX'.
	Reason: The project ‘test1’ is damaged and cannot be opened due to a parse error. Examine the project file for invalid edits or unresolved source control conflicts.

Path: /Users/mou/Documents/HISE Projects/test1/Binaries/Builds/MacOSX/test1.xcodeproj



Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Prozess beendet]

@DanH Yes, I can open Projucer normally.

[Christoph Hart]

xcodebuild: error: Unable to read project 'test1.xcodeproj' from folder

Looks like you've corrupted the project files somehow. Does this happen if you delete the entire Builds folder and try again?

[Oli Ullmann]

@Christoph-Hart
I created a completely new project again, but unfortunately it still crashes. Here is the error report:

Last login: Tue Jan 20 09:35:36 on ttys000
/Users/mou/Documents/HISE\ Projects/newTest/Binaries/batchCompileOSX ; exit;
mou@Marks-Mac-Pro ~ % /Users/mou/Documents/HISE\ Projects/newTest/Binaries/batchCompileOSX ; exit;
Re-saving file: /Users/mou/Documents/HISE Projects/newTest/Binaries/AutogeneratedProject.jucer
Finished saving: Visual Studio 2017
Finished saving: Xcode (macOS)
Finished saving: Xcode (iOS)
Finished saving: Linux Makefile
Compiling Instrument plugin newTest ...

----- xcbeautify -----
Version: 2.28.0
----------------------

2026-01-20 11:41:01.534 xcodebuild[2378:93646] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
2026-01-20 11:41:02.291 xcodebuild[2378:93646] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 874. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug.
2026-01-20 11:41:02.291 xcodebuild[2378:93646] Error Domain=NSCocoaErrorDomain Code=3840 "JSON text did not start with array or object and option to allow fragments not set. around line 1, column 0." UserInfo={NSDebugDescription=JSON text did not start with array or object and option to allow fragments not set. around line 1, column 0., NSJSONSerializationErrorIndex=0}
2026-01-20 11:41:02.293 xcodebuild[2378:93646] Writing error result bundle to /var/folders/qx/0_mrj8z91hd2gj5y61xxknvw0000gn/T/ResultBundle_2026-20-01_11-41-0002.xcresult
xcodebuild: error: Unable to read project 'newTest.xcodeproj' from folder '/Users/mou/Documents/HISE Projects/newTest/Binaries/Builds/MacOSX'.
	Reason: The project ‘newTest’ is damaged and cannot be opened due to a parse error. Examine the project file for invalid edits or unresolved source control conflicts.

Path: /Users/mou/Documents/HISE Projects/newTest/Binaries/Builds/MacOSX/newTest.xcodeproj



Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Prozess beendet]

[Christoph Hart]

Yeah, that looks like something's off on your machine, the CI build is OK and compiles the test project on macOS.

Try pasting the compiler output into ChatGPT, it gives you a list of things to check. Whether this solves it or not, I don't know, could be anything from a weird project name to an invalid developer certificate.

[Oli Ullmann]

@Christoph-Hart

All right, thank you very much. I'll start looking into it. :-)
Compiling has always worked so far, and I haven't changed anything in the system. I'll give you feedback when I find the error.

[Oli Ullmann]

@Christoph-Hart
Okay, I always create a backup of the last working HISE version before compiling a new one. This one still works! Unfortunately, the commit is not displayed in HISE, but since I compiled it on December 21, 2025, I assume it is commit 6ba56cc. That is the last one that works for me.

Could it be that my xCode version is too old for the current HISE version?
I am working with xCode version 14.3.1 (14E300c).

[David Healey]

@Oli-Ullmann said in HISE crashes when loading my project:

I assume it is commit 6ba56cc.

Compile it and see ;)

[Oli Ullmann]

@David-Healey
Okay, I cloned HISE again with git clone https://github.com/christophhart/HISE.git then switched to the corresponding commit with git reset --hard 6ba56cc and recompiled HISE. (I used git clone without the new commands because I don't need the JUCE 8 elements for the old commit.)

HISE still does not show me any commit information. When I enter git commit in the console, I only see the following text: Your branch is behind 'origin/develop' by 80 commits.

Maybe this is because Christoph created an initial commit on January 8.

Anyway, everything works with the commit 6ba56cc. With later commits, I can no longer compile plug-ins from HISE. I have no idea why this is and can only assume that it might be due to my xCode version. Because the xCode projects created with the current HISE version cannot be opened with xCode.

So maybe I should update it. Which xCode version are you using, Dave?

[David Healey]

@Oli-Ullmann I'm not sure which one I'm using at the moment, just try the latest one supported by your OS version: https://xcodereleases.com/

[Oli Ullmann]

@David-Healey
I'll do that.