Paul Sweeney

Amazing! This is really narrowing it down now. :) What happens with these: ```codesign -d -v out/Dock\ Window\ Preview.app/Contents/MacOS/dock-window-preview``` (confirm signature) ```codesign --sign - out/Dock\ Window\ Preview.app/Contents/MacOS/dock-window-preview``` ```codesign --force --sign...

Excellent! Thanks again for your help on this! I think this all just comes down to how Yode is bundled. One last thing to try if you don't mind: ```...

Will have to research more, and open a ticket on ```yackage``` to see if the author has been encountering this issue. The lack of access to an M1 makes it...

You could have fooled me, would have assumed you were a software engineer! 😂 That confirms it so, it's not liking the fact that ```yode``` was modified. The permissions work...

It's possible ```13.0``` breaks some of the native Objective-C code. This app uses some private APIs, so it's possible those have changed. Although I would have expected to see an...

Updated the code to include some additional useful debug messages. :)

Another test to try. I noticed that sometimes Mac doesn't let you sign over binaries if they have an issue with their existing signature. Try to remove the signature first,...

Did the additional debug messages show additional information when using ```npm start```? Did the ```--remove-signature``` command throw any error at all? If you used ```codesign -d -v``` will it say...

Custom build script that in theory, should allow signing. * Clone the repo. * If dependencies have not been installed with ```npm install```, install them. * Create a file called...

Brilliant! I'll update the installation script, thanks for confirming! :) As for it not showing anything beyond that, when you try running through the terminal, what do the logs say...