Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verification error on macOS Catalina #48

Open
Chap92 opened this issue Feb 9, 2020 · 4 comments
Open

Verification error on macOS Catalina #48

Chap92 opened this issue Feb 9, 2020 · 4 comments

Comments

@Chap92
Copy link

Chap92 commented Feb 9, 2020

When you try to run font-manager on macOS Catalina, you get an error: "fontmanager.node" cannot be opened because the developer cannot be verified. Will notorization resolve this issue?

@devongovett
Copy link
Member

What do you mean by "run"? Could you give a code example? It works for me on Catalina.

@Chap92
Copy link
Author

Chap92 commented Feb 9, 2020

Does it work without getting it notarized? I tried to integrate font-manager into an Adobe CEP extension, which uses Node.js v7.7.4. font-manager was locally installed in the folder of the extension. The extension works as expected in macOS High Sierra and Mojave, but gives the above error in Catalina: ("fontmanager.node" cannot be opened because the developer cannot be verified). I'm guessing the C++ source files have to be re-compiled and notarized for it to work correctly?

@devongovett
Copy link
Member

Yeah I didn't do anything to notarize it. You're getting that with just require('font-manager')?

@Chap92
Copy link
Author

Chap92 commented Feb 10, 2020

No, the error does not come with just require ('font-manager'). The error pops-up when you try to invoke function getAvailableFonts ():

	app.get ("/get-fonts", (req,res,next) => {
		fontManager.getAvailableFonts(function(fonts) { 
			res.status(200).send(fonts);
		});
	
	});

I'm guessing that is the point where it tries to access fontmanager.node. Did you make any changes to your machine to disable Gatekeeper? Like sudo spctl --master-disable maybe?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants