Not sure if this will resolve this particular issue, but the same error in a different context was resolved by switching the SSL backend in curl to Apple native Secure Transport by setting CURL_SSL_BACKEND=SecureTransport.
ptrbchl
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution