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
Library not loaded: @rpath/libswiftAccelerate.dylib #903
Comments
@Dschee Not sure what could cause it, but it is more likely an issue that the test bundle (target) does not contain |
Already tried that, didn't work. Found a workaround: Using HanekeSwift now instead of Kingfisher. ;) |
Great! |
Sorry for being rude, shouldn't have made a joke about it, was disrespectful. |
@Dschee No, don't worry guy. I was not angry at all. 😂 Thanks for taking time on trying this project and opening the issue. I am sorry that I didn't help you out and I'd take a look at it when I have a chance later since it is weird to me. |
Ah, ok, then I overknterpreted things. Anyways, was rude. ^^ By the way, the project structure where I integrated this os weird, too. If I were you I‘d keep in the back of my mind that there was such an issue bbt won‘t do anything about it unless someone else would run into similar problems. But it‘s weird in any case ... |
Sure. Maybe you were importing or using Kingfisher’s method in the UI test target, which did not make sense and should not happen in fact. I would try to see whether I can reproduce it later, but if I cannot, I will just let it go. Thanks! |
Hello @onevcat. I have the same issue.
Any ideas on how to fix it? |
Solved by importing accelerate in the header file of the networking framework (where kf is imported):
|
Try clean build folder |
@GWesley clean build folder made it work for me, I don't think this is related to Kingfisher |
Adding the imports didn't worked for me, neither cleaning build folder. Not even adding Accelerate.framework to the "Link Binary with Libraries" phase Any other ideas? |
I am also running into this issue. Changing @rpath settings for my project hasn't resulted in a compiled UI test either.
|
One alternative is to fork Kingfisher and remove everything related to Accelerate. It's basically just removing the "blur" feature anyway, so I think it won't be an issue for most people |
I fixed this with adding |
The same here. I've removed |
The issue is still happening why was it closed? I get the same issue on my test target |
Kingfisher relies on Accelerate framework to do fast blur processor. In an app target, Xcode could find these kinds of implicit dependencies automatically and link them when necessary. But in a test target, it seems that Xcode has some issues to find implicit dependencies, so you need to add the Accelerate.framework to the linked binary section in build setting yourself manually. |
@gal-orlanczyk Inspired by: |
@onevcat Still not working by your solution. Build setting didn't have linked binary section. |
Issue Description
What
When including Kingfisher using latest Carthage in a project which has subprojects as components, when running one of the subprojects tests we get the following error:
Other Comment
As you can see it seems there's an issue with the
Accellerate
framework which is included. I'm guessing that since the dependency isn't placed directly into the component project, Xcode has problems including the implicit dependency without explicitly stating where it is. The usual search paths (I know about @loader_path and @rpaths – already tried those approaches to fix this) seem not to be enough.The text was updated successfully, but these errors were encountered: