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

Differently signed dart from brew prevents loading C library #41

Closed
Buggaboo opened this issue Oct 20, 2019 · 2 comments
Closed

Differently signed dart from brew prevents loading C library #41

Buggaboo opened this issue Oct 20, 2019 · 2 comments
Labels
bug Something isn't working

Comments

@Buggaboo
Copy link
Contributor

Buggaboo commented Oct 20, 2019

I got this, by moving the lib one level lower (project root):

...
 Invalid argument(s): Failed to load dynamic library (dlopen(libobjectbox.dylib, 1): no suitable image found.  Did find:
        libobjectbox.dylib: code signature in (libobjectbox.dylib) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.)
  dart:ffi                                             new DynamicLibrary.open
...

It might be a new security thing. I'm not the only one. According to this thread, we either need objectbox's or dart's signing key, or remove the signing hash from the compiling dart binary. I fixed it by doing the last bit.

From bash or zsh wherever:

codesign --remove-signature `which dart`

Originally posted by @Buggaboo in https://github.com/objectbox/objectbox-dart/timeline

@vaind vaind added the bug Something isn't working label Oct 21, 2019
@vaind
Copy link
Collaborator

vaind commented Oct 25, 2019

There isn't much we can do at the moment. Signing the library wouldn't help either because all libraries need to be signed by the same developer (app publisher).

At least for now, let's wait and see how it's resolved in the Dart SDK issue you've linked

@vaind
Copy link
Collaborator

vaind commented Aug 4, 2020

I don't think this is an issue anymore with the changes landing in dart/flutter binaries, right? Closing this but feel free to comment in case you think there's something more to be done on objectbox-dart side instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants