You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're having trouble running one of our extensions from IntelliCode on MacOSX.
After debugging the process, it seems like our process is throwing an exception when it tries to load libonnxruntime.dylib because it seems the binaries are not properly signed (It complains about missing Team Name on the signing).
I've downloaded the binaries from the Nuget Package, and the artifacts output from this repo, and ran a codesign -v libonnxruntime.dylib on the binaries and I'm getting result of 'code object is not signed at all'.
I'm wondering if this is an issue on our end, or if in fact the MacOS binaries you are distributing are not signed.
I would really appreciate some guidance on this, as we need to determine whether we should be doing our own signing, even though it's a third party library.
Thanks!
To reproduce
Download any version of OnnxRuntime compatible with MacOSx and try to run it or do a codesign -v to verify it's signature.
Urgency
This is blocking an upcoming release, and we want to just make sure we're not doing anything wrong before we try to sign it ourselves.
Platform
Mac
OS Version
12.6.6
ONNX Runtime Installation
Released Package
ONNX Runtime Version or Commit ID
latest
ONNX Runtime API
C#
Architecture
X64
Execution Provider
Other / Unknown
Execution Provider Library Version
No response
The text was updated successfully, but these errors were encountered:
@mszhanyi, could you please help? If you have any questions, please create an email thread. Here is not a good place to talk about the details of signing.
Describe the issue
We're having trouble running one of our extensions from IntelliCode on MacOSX.
After debugging the process, it seems like our process is throwing an exception when it tries to load libonnxruntime.dylib because it seems the binaries are not properly signed (It complains about missing Team Name on the signing).
I've downloaded the binaries from the Nuget Package, and the artifacts output from this repo, and ran a
codesign -v libonnxruntime.dylib
on the binaries and I'm getting result of 'code object is not signed at all'.I'm wondering if this is an issue on our end, or if in fact the MacOS binaries you are distributing are not signed.
I would really appreciate some guidance on this, as we need to determine whether we should be doing our own signing, even though it's a third party library.
Thanks!
To reproduce
Download any version of OnnxRuntime compatible with MacOSx and try to run it or do a codesign -v to verify it's signature.
Urgency
This is blocking an upcoming release, and we want to just make sure we're not doing anything wrong before we try to sign it ourselves.
Platform
Mac
OS Version
12.6.6
ONNX Runtime Installation
Released Package
ONNX Runtime Version or Commit ID
latest
ONNX Runtime API
C#
Architecture
X64
Execution Provider
Other / Unknown
Execution Provider Library Version
No response
The text was updated successfully, but these errors were encountered: