Bug #4617
closed

macOS Catalina error: “libsaxonpec.dylib” cannot be opened because the developer cannot be verified.
100%
Description
I tried to run the sample C++ program with Saxon/C on macOS Catalina 10.15.4. Getting the following error:
macOS Catalina error: “libsaxonpec.dylib” cannot be opened because the developer cannot be verified.
There is an update in Excelsior JET 15.3 for OS X Notarization for signing applications on Mac OS.
We will look to apply this in the next release of Saxon /C
See the workaround:
In the Finder on your Mac, locate the Saxon/C dylib file (i.e. libsaxonpec.dylib). Control-click the app icon, then choose Open from the shortcut menu. Click Open. The app is saved as an exception to your security settings, and you can open it in the future by double-clicking it or from cli, just as you can with any authorised app.
Updated by Norm Tovey-Walsh over 1 year ago
Yes, this is gatekeeper. A simple way to work around it is to run:
xattr -d -r com.apple.quarantine .
in the directory where you unzipped the distribution.
I've been trying to get code signing and notarization working and will add SaxonC to the mix.
Updated by O'Neil Delpratt 11 months ago
- Found in version changed from 1.2.1 to 1.2.1, 12.0
This bug issue is still failing in SaxonC 12. We are still investigating a solution.
Updated by Norm Tovey-Walsh 10 months ago
I wasn't able to reproduce this with Saxon 12 on intel or ARM hardware. Are there instructions anywhere for reproducing the problem with 12?
Updated by O'Neil Delpratt 10 months ago
You should be able to reproduce the error by following the C++ samples instructions here: https://www.saxonica.com/saxon-c/documentation12/index.html#!starting/running
I did the following to reproduce the error:
sudo cp libs/darwin/libsaxon-hec-12.0.dylib /usr/local/lib/.
cd samples/cppTests
./build64-mac.sh
./testXPath
This is on MacOS 12,5,1
Updated by O'Neil Delpratt 10 months ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Bug fixed for the next maintenance release.
Updated by O'Neil Delpratt 9 months ago
- Status changed from Resolved to Closed
- Fixed in version set to 12.1
Bug fixed applied in the SaxonC 12.1 maintenance release.
Please register to edit this issue