SwiftPrivilegedHelper: Bless Error: Error Domain=CFErrorDomainLaunchd Code=4 "(null)"

Hi Eric this is really awesome thats you help us to use it , thank you

now issue No : 1

Helper: Bundle Version => 1.0.3
2018-03-25 19:13:11.077457+0530 MyApplication[2122:36235] Bless Error: Error Domain=CFErrorDomainLaunchd Code=4 "(null)"
2018-03-25 19:13:11.077690+0530 MyApplication[2122:36158] XPC Connection Invalidated

Issue No: 2

SMJobBlessUtil.py: tool designated requirement (identifier "com.github.erikberglund.MyApplicationHelper" and anchor apple generic and certificate leaf[subject.CN] = "Mac Developer: ****** (827NYLK373)" and certificate 1[field.1.2.840.113635.100.6.2.1] /* exists */) doesn't match entry in 'SMPrivilegedExecutables' (anchor apple generic and identifier "com.github.erikberglund.MyApplicationHelper" and (certificate leaf[field.1.2.840.113635.100.6.1.9] /* exists */ or certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = 827NYLK373 ))

i just change team id , rest everything is intact …

question : do i need to create a identifier at itunes connect ?

Thanks

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 21 (10 by maintainers)

Most upvoted comments

The error message you got said that it had set “$(PRODUCT_BUNDLE_IDENTIFIER)” as the bundle identifier for the helper, and that should not be possible if you did not create a new info plist for the helper, or changed that manually.

I have also found that this variable works normally to ge the bundle identifier, but in the helper it’s not expanded to the correct value so one has to set that string explicitly.

If you used Xcode to change the bundle identifiers it might have been “smart” and done that for you and that could also have made it not work.

When I tested only changing the bundle identifier for the project and in the script it has worked as expected, so I have not been able to reproduce this.

I should probably add a message that the script is only to make things easier to test as automatic signing is enabled.

Thanks for your report

erikberglund on Oct 25, 2018

@erikberglund I did. Did an entire search of the old bundle id’s and there wasn’t a single string left in the project pointing to them. I just ran ./SMJobBlessUtil.py setreq and now it works, maybe make it part of the readme? (or I did something wrong, but I can’t seem to pinpoint what exactly)

Thanks regardless, for answering my dumb questions 😃

jariz on Oct 25, 2018

@analyticd @insanelydeepak Sorry for the delay, but now it’s updated with some improvements.

First, the signing is automated, so you should not have to update the code requirements with your own singing information.

I also added some mitigations for a common attack vector where the helper not validates the calling application’s code signature to match the helper.

So, please try the newer version and open a new issue for any issues you run into.

erikberglund on Oct 5, 2018