Kingfisher
Kingfisher copied to clipboard
Module Not Found - Unable to load standard library for target 'arm64-apple-ios10.0'
Having an issue building on Xcode 12 GM. I can successfully build for a real device and for Generic iOS Device. But when trying to build for any simulator I get the following 2 failures:
No such module Kingfisher Unable to load standard library for target 'arm64-apple-ios10.0'
Any ideas on a fix here? Weirdly enough I cannot even get Xcode 12 to create an iOS 10 simulator. and the simulators im trying to build for are 13.5 and 14.0
No idea what can cause it. It is not likely to be what we can solve in Kingfisher, since Xcode should being respecting your project settings when build a project and Kingfisher can just follow the instruction of the build system.
By the way, may I know how did you add Kingfisher to your project? Can it be a problem of the dependency manager like Carthage or so?
I am facing similar error on Xcode 12 for other framework @jasonhr13. Let me know if you are able to solve it.
Not sure what you are using to install Kingfisher. But if you are using the xcframework, I heard that there is a bug in Xcode 12 GM that it is picking the wrong slice so you may have this issue. Reverting back to use Xcode 12 beta 6 or choose another way to install the framework might solve it.
(But I didn't verify it myself.)
I personally cannot reproduce this issue in my environment. Can anyone help provide some reproducible steps? Or can you prepare a simple sample in which this can happen?
Some more information would be also helpful for tracking it quicker:
- Are you using an ARM Mac? Or a traditional Intel mac? The official released Xcode 12.0 does not support ARM Mac yet, you need to keep to use beta 6.
- By which way you are installing Kingfisher? Pods, Carthage or SPM?
- Does this error happens when you click the Run button in Xcode? Or does it happen when you build with command line?
Thanks for any information.
I have the same issue when using KingFisher in my framework project and building for the simulator
The problem is not occurring when building for a physical device
Note *In previous versions of Xcode, this was not a problem
Set build active architecture to NO to see the problem