4

I've installed SDWebImage in my Xcode 5 / iOS 7 project, but building gives me the following issue which will result in a fatal exception:

ignoring file SDWebImage.framework/SDWebImage, missing required architecture x86_64 in file SDWebImage.framework/SDWebImage

SDWebImage seems to be cause this issue with Google Analytics, and the best resolution seems to be cutting arm64 by using Standard architectures (armv7, armv7s) in one's build settings. I don't really want to do that, and SDWebImage had this issue blaming libwebp which suggested falling back to framework 3.2 temporarily.

I'm running framework 3.5 already. Does anyone know how to resolve this, or am I stuck with these work-arounds?

(Thanks!)

Community
  • 1
  • 1
LordParsley
  • 3,808
  • 2
  • 30
  • 41

5 Answers5

4

As of now, this is fixed in the master branch, but it is not included in the latest .framework release. What I did to make it work was this:

1) Download the latest release from the master branch (currently https://github.com/rs/SDWebImage/releases/tag/3.5.3)

2) Remove SDWebImage.framework from my project.

3) Copy the source files from the zip (Everything inside SDWebImage + the files NSData+ImageContentType.h and NSData+ImageContentType.m) into my project.

4) Replace the header includes of to "SDWebImage.../...h"

Might be a better way to do this, but this solved the problem for me. As I understand it,64-bit support will be added to the next proper release.

Reason
  • 1,410
  • 12
  • 33
  • 1
    Much appreciated! I see it has indeed been released with 3.5.4 over here https://github.com/rs/SDWebImage/releases/tag/3.5.4 – LordParsley Mar 13 '14 at 12:43
  • Strange, I still get the same error even after replacing the old .framework with 3.5.4. https://github.com/rs/SDWebImage/releases/tag/3.5.4 Is there any way to verify it's the correct version? – MdaG Mar 13 '14 at 15:13
  • Just a note that the framework release available via Cocoapods has been available since last year now. – LordParsley Mar 10 '15 at 08:15
  • Thank you so much!! I was having this issue with the latest version of SDWebImage in 2019, much prefer this manual source code import approach... it's just so much easier. – Supertecnoboff Nov 07 '19 at 16:21
1

Had similar problem with SDWebImage 3.7.0 in my case what helped was updating CocoaPods to 0.33.1, then reinstalling SDWebImage pod and cleaning project

Michal Gumny
  • 1,770
  • 1
  • 16
  • 24
1

Download newest version of SDWebImage (3.7.1.4) can solve this problem

I had this issue too, and done.

tuan
  • 11
  • 1
0

Try again with "Other Linker Flags" set to -all_load instead of -ObjC

As per https://github.com/rs/SDWebImage/issues/494, there's only a workaround for now, it is definitely a problem with libwebp.

Jeremiah Smith
  • 740
  • 6
  • 17
0

Just wondering are you running your app in the simulator? Is there a pressing reason why you must run the simulator using the 64-bit mode? I was having the same problem you are having but it went away as soon as I began using the 32-bit mode. Since it looks like the problem is quite fundamental, perhaps the best thing to do for now is to use the 32-bit mode of the simulator and wait for a fix.

mr.sosa
  • 691
  • 7
  • 13