ios – The best way to Use Community Extension and Endpoint Safety Entitlements with a Private Account and Offered Certificates/Profiles in Xcode?

0
20
ios – The best way to Use Community Extension and Endpoint Safety Entitlements with a Private Account and Offered Certificates/Profiles in Xcode?


In my undertaking, I would like to make use of the Community Extension and Endpoint Safety entitlements. My private account does not have the required developer permissions. I requested our improvement group admin to assist, and so they configured the required entitlements for me. They offered a .p12 certificates and a provisioning profile, each sure to the bundle ID.

Screenshot

Screenshot

Nonetheless, within the “Signal & Capabilities” part of Xcode, the one out there group is my private account. I can also’t add the required frameworks by way of “Add Functionality.”

How can I take advantage of the offered certificates and provisioning profile to allow the required entitlements? Or is there any further configuration that the admin must do on their finish?

I’ve already tried disabling SIP to make use of the frameworks, however I encountered the error:

Didn’t open service: Bxe80082e6: Caller will not be entitled to hook up with EndpointSecurity.

After I used codesign to forcibly change the entitlements, the method was killed each time it ran, and there have been no associated logs within the Console.

>>codesign --force --sign "Mac Developer: " --entitlements process_monitor.entitlements process_monitor
process_monitor: changing current signature

>>codesign -d --entitlements :- process_monitor
Executable=/Customers/admin/Library/Developer/Xcode/DerivedData/process_monitor-hkikjlukpyqdmmbvkgsdebtutlpn/Construct/Merchandise/Debug/process_monitor
warning: Specifying ':' within the path is deprecated and won't work in a future launch
com.apple.developer.endpoint-security.shopper

>>sudo ./process_monitor
[1]    40982 killed     sudo ./process_monitor

>>sudo ./process_monitor
[1]    40908 killed     sudo ./process_monitor

>>sudo ./process_monitor
[1]    34376 killed     sudo ./process_monitor

>>sudo ./process_monitor
[1]    40982 killed     sudo ./process_monitor

I mentioned this with the event group and requested if they may add my account to the event group. Their response was that they often deal with signing utilizing certificates and provisioning profiles, as their work doesn’t contain calling particular entitlements.

I couldn’t discover any public documentation on-line explaining this case. If attainable, may you verify whether or not becoming a member of the event group is obligatory on this case? This fashion, I can request them so as to add me to the group.

LEAVE A REPLY

Please enter your comment!
Please enter your name here