Post

Replies

Boosts

Views

Activity

Reply to Endpoint Security Frameworks SDK - Not foudn for download
For development , we were facing issue while compiling application, Apple has approved our request of endpoint security entitlements #1 _es_new_client, referenced from: AppNameFileControl.ExtensionMain.(startESClient in _6F8923D12EE413BBE2532B27F937A19F)() -> () in ExtensionMain.o _es_respond_auth_result, referenced from: closure #1 (Swift.OpaquePointer, Swift.UnsafePointer<__C.es_message_t>) -> () in AppNameFileControl.ExtensionMain.(startESClient in _6F8923D12EE413BBE2532B27F937A19F)() -> () in ExtensionMain.o closure #1 (Swift.OpaquePointer, Swift.UnsafePointer<__C.es_message_t>) -> () in AppNameFileControl.ExtensionMain.(startESClient in _6F8923D12EE413BBE2532B27F937A19F)() -> () in ExtensionMain.o _es_subscribe, referenced from: AppNameFileControl.ExtensionMain.(startESClient in _6F8923D12EE413BBE2532B27F937A19F)() -> () in ExtensionMain.o #2 error: link command failed with exit code 1 (use -v to see invocation) ld: framework 'EndpointSecurity' not found clang: error: linker command failed with exit code 1 (use -v to see invocation) error: fatalError
Topic: App & System Services SubTopic: Core OS Tags:
Oct ’25
Reply to codesign not signing .app MacOS executable 'can't verify signature'
Thanks @eskimo Tried all the steps above. Can you please share any internet article or video to perform given steps. Regards
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Dec ’23
Reply to codesign not signing .app MacOS executable 'can't verify signature'
Found out solution, we were not using ditto for extracting the application causing sign loss. Ticket can be closed
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Oct ’25
Reply to Endpoint Security Frameworks SDK - Not foudn for download
For development , we were facing issue while compiling application, Apple has approved our request of endpoint security entitlements #1 _es_new_client, referenced from: AppNameFileControl.ExtensionMain.(startESClient in _6F8923D12EE413BBE2532B27F937A19F)() -> () in ExtensionMain.o _es_respond_auth_result, referenced from: closure #1 (Swift.OpaquePointer, Swift.UnsafePointer<__C.es_message_t>) -> () in AppNameFileControl.ExtensionMain.(startESClient in _6F8923D12EE413BBE2532B27F937A19F)() -> () in ExtensionMain.o closure #1 (Swift.OpaquePointer, Swift.UnsafePointer<__C.es_message_t>) -> () in AppNameFileControl.ExtensionMain.(startESClient in _6F8923D12EE413BBE2532B27F937A19F)() -> () in ExtensionMain.o _es_subscribe, referenced from: AppNameFileControl.ExtensionMain.(startESClient in _6F8923D12EE413BBE2532B27F937A19F)() -> () in ExtensionMain.o #2 error: link command failed with exit code 1 (use -v to see invocation) ld: framework 'EndpointSecurity' not found clang: error: linker command failed with exit code 1 (use -v to see invocation) error: fatalError
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Oct ’25