10.14.3 building for 10.10.5 (32-bit) (crashing)

Greetings!

Recently we have setup another build mac to build our main application using the same build resources (managed with git).

New build mac: 10.14.3
Old build mac: 10.11.1

The main issue encountered with the new mac causes only our 32-bit built product to crash on launch for 10.10.5. (whereas building the same 32-bit app off the same branch and using the same build resources on the old build mac, launches as expected on 10.10.5).

64-bit apps work fine.

One flag worth mentioning we found was:
– code signing the product on the new build mac causes the product to crash on launch for 10.10.5
– not code signing the product on the new build mac causes the product to launch successfully.

I have tested code signing another app built from the new build mac, and running this on 10.10.5, this ran successfully.

The only stack i have been able to obtain is this:

RuntimeRaiseException
_Z14RaiseExceptionPKcS0_mi
_ZL8HashFileP20REALfolderItemStructa.966
SHA1MBS.!HashFile%s%ob
server_log.!accum_hash_report%%oA1s
server_log.!accum_hash_report%%oA1s
server_log.!accum_hash_report%%oA1s
server_log.!accum_hash_report%%oA1s
server_log.!generate_hash_report%s%
server_log.Constructor%%o<server_log>oo
Studio_Main.UnhandledException%b%o
App.Event_UnhandledException%b%oo
Application._CallFunctionWithExceptionHandling%%op
_Z33CallFunctionWithExceptionHandlingPFvvE
XojoFramework$5053
-[NSApplication run]
_Z8mainloopv
RuntimeRun
REALbasic._RuntimeRun
_Main
main
start

if anyone is wondering what script we use for code signing, its here (shell script):
#!/bin/sh
#1 = path to app

xattr -cr “$1”

#determine how deep our deepest depth of the directory, this will allow us to codesign from bottom level up
i=$(sh get_directory_depth.sh “$1”)

while [[ $i != -1 ]]
do
find “$1” -name “*.app” -maxdepth $i -mindepth $i -exec codesign --verbose=4 -s “[CERTIFICATE]” -f --deep {} \;
i=$((i - 1))
done

If anyone has any ideas/require more information, please feel free to get in touch!

All the best,

Connor

That looks like an MBS plugin problem…

Have you checked the name and message of that exception?

E.g. an exception due to nil folderitem passed?