macOS 26 Launch Constraints

Question

Created 2d

Replies 6

Boosts 0

Participants 2

I've recently upgraded to the RC candidates of macOS 26 and Xcode 26. The app I'm building has a helper tool using SMAppService. When I run the app and helper tool in macOS 15 or macOS 26, all works as expected. When it runs on macOS 13 or 14, which previously worked. The helper now crashes on launch with the following reason:

Termination Reason: CODESIGNING 4 Launch Constraint Violation

I found this developer session which seems to address this, but the plist I've added doesn't seem to satisfy the constraint.

https://developer.apple.com/videos/play/wwdc2023/10266/

Here are the contents of my new plist:

<plist version="1.0"> <dict> <key>team-identifier</key> <string>MYTEAMID</string> <key>signing-identifier</key> <string>com.myteam.myapp</string> </dict> </plist>

Are there any gotchas here that I might be missing?

Thanks!

Answered by DTS Engineer in 857914022

it seems to be the remedy to the helper/daemon crash.

That’s unlikely. Launch contraints typically cause things to fail rather than make things work. Hence the constraint.

My advice here is that you remove anything you’ve done with regards launch constraints and then debug the original problem you were seeing. If that’s a crash and you post a crash report, I’d be happy to take a look.

See Posting a Crash Report for advice on how to post a crash report.

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

Boost

Answer 1

ski4funSonoma OP

2d

I should add, that using codesign -d -vvvv to interrogate my helper, it doesn't appear that the parent process plist (.coderequirement) is getting embedded in my command-line helper tool. The info.plist IS getting embedded, however.

0

Answer 2

DTS Engineer OP

Apple

1d

I’m confused by your overall goal here. What are you trying to do with launch contraints?

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

0

Answer 3

ski4funSonoma OP

1d

When building as described above, the helper crashes in such a way (Termination Reason: CODESIGNING 4 Launch Constraint Violation) that suggests I need to apply launch constraints to resolve the problem. I had not previously had launch constraints in my project.

0

Answer 4

DTS Engineer OP

Apple

20h

I understand what the symptoms are. I’d like to know what your goal is in applying a launch constraint in the first place. What are you actually trying to constrain? And why?

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

0

Answer 5

ski4funSonoma OP

11h

I'm only attempting to apply launch constraints because it seems to be the remedy to the helper/daemon crash. If there is a simpler remedy (like a new build setting I'm missing in XCode 26?) that would be even better.

Mainly, I'm confused as to why building with XCode 26 and linking with macOS 26 would cause a crash with that code signing reason when previously it did not.

0

Answer 6

DTS Engineer OP

Apple

2h

Recommended

it seems to be the remedy to the helper/daemon crash.

That’s unlikely. Launch contraints typically cause things to fail rather than make things work. Hence the constraint.

My advice here is that you remove anything you’ve done with regards launch constraints and then debug the original problem you were seeing. If that’s a crash and you post a crash report, I’d be happy to take a look.

See Posting a Crash Report for advice on how to post a crash report.

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

0