The es_copy_message function is deprecated and there are no alternatives provided.
https://developer.apple.com/documentation/endpointsecurity/3228861-es_copy_message
Currently, we copy incoming messages so that we can respond to messages later on a different dispatch queue/thread.
Is there a change in ownership of incoming messages or is there something that I am missing here?
https://developer.apple.com/documentation/endpointsecurity/3228861-es_copy_message
Currently, we copy incoming messages so that we can respond to messages later on a different dispatch queue/thread.
Is there a change in ownership of incoming messages or is there something that I am missing here?
From the header file
/**
APIUNAVAILABLE(ios, tvos, watchos)
esmessaget * Nullable
escopymessage(const esmessaget * _Nonnull msg);
/**
- Retains an esmessaget, returning a non-const pointer to the given esmessaget for compatibility with
- * @warning It is invalid to attempt to write to the returned esmessaget, despite being non-const, and
- * @deprecated Use esretainmessage to retain a message.
- @param msg The message to be retained
- * @brief The caller must release the memory with es_free_message
/
APIUNAVAILABLE(ios, tvos, watchos)
esmessaget * Nullable
escopymessage(const esmessaget * _Nonnull msg);