macOS13 system make our process crash

Question

Created Dec ’22

Replies 2

Boosts 0

Participants 2

Hi Team,

We have build a developer ID level signed package with notarize successfully, we test the package on macOS12, it run succeed. But the same package we installed on macOS13, it failed and report our process named "XTService" crashed.

The Crash log is: Library not loaded: @rpath/FMDB.framework/Versions/A/FMDB "/Applications/XTApp.app/Contents/Resources/bin/XTService.app/Contents/Frameworks/FMDB.framework/Versions/A/FMDB' (code signature invalid in <90A347C8-9899-351A-818A-20984EFD00B5> '/Applications/XTApp.app/Contents/Resources/bin/XTService.app/Contents/Frameworks/FMDB.framework/Versions/A/FMDB' (errno=1) sliceOffset=0x00034000, codeBlobOffset=0x00029420, codeBlobSize=0x00005050)"

I use the codesign tool to check the FMDB file strictly, it shows it's valid on the disk. So I think the issue may in system level, and it have some relation with this thread https://developer.apple.com/forums/thread/128435 (which issue in IOS)

PS:

My Xcode was signed with paid account, and the package perform normal on macOS12
I use CocoaPods to manage the 3rd party libraries, and I ensure the signature is correct

截屏2022-12-12 16.28.20.png

Boost

Answer 1

DTS Engineer OP

Apple

Dec ’22

Accepted Answer

This problem is almost certainly an issue with the way that you sign your code. For general background on that, see:

I also have a bunch of info about debugging trusted execution problems like this, rooted at Resolving Trusted Execution Problems. One of those posts, Resolving Library Loading Problems, has a Restricted Entitlements on Library Code section that I suspect explains your issue.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1

Answer 2

jiangsen OP

Dec ’22

Thank you Eskimo! After I modified the code sign scripts with removing the "deep" options, the issues no happen on macOS13.

0