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

Xcode13 canImport is not recognized #1816

Closed
SummerTimer2016 opened this issue Sep 23, 2021 · 10 comments
Closed

Xcode13 canImport is not recognized #1816

SummerTimer2016 opened this issue Sep 23, 2021 · 10 comments

Comments

@SummerTimer2016
Copy link

use Xcode13 Archive , happen not find 'Binding' and not find 'Image'

@DeadHipo
Copy link

DeadHipo commented Sep 23, 2021

++

@DeadHipo
Copy link

Reproduced when use SwiftPM, maybe problem here #if canImport(SwiftUI) && canImport(Combine)

Add via cocoapods solve problem

@EdgarDegas
Copy link

You guys should browse the existing issues before creating a new one.

Anyway, the resolution is rather simple: upgrade to Kingfisher 7.0.0. While it might be also catastrophic depending on your project, since you have to drop support for all users under iOS 12.0.

Check issue#1802 and issue#1725. Also this migration guide.

@Arrankar
Copy link

Hello. Version 7.0, but still have troubles with building. Has anyone solved this problem?

Снимок экрана 2021-09-23 в 20 34 32

@EdgarDegas
Copy link

Hello. Version 7.0, but still have troubles with building. Has anyone solved this problem?

Снимок экрана 2021-09-23 в 20 34 32

iOS < 12.0 is no longer supported.

@Arrankar
Copy link

Hello. Version 7.0, but still have troubles with building. Has anyone solved this problem?
Снимок экрана 2021-09-23 в 20 34 32

iOS < 12.0 is no longer supported.

Thank u! I solved the problem by correcting iOS 10 to iOS 12 in my PodFile.

post_install do |installer|
 installer.pods_project.targets.each do |target|
  target.build_configurations.each do |config|
   config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.0'
  end
 end
end

@andrei115
Copy link

You guys should browse the existing issues before creating a new one.

Anyway, the resolution is rather simple: upgrade to Kingfisher 7.0.0. While it might be also catastrophic depending on your project, since you have to drop support for all users under iOS 12.0.

Check issue#1802 and issue#1725. Also this migration guide.

It's not catastrofic to drop support for iOS 12.0, but it is to drop support for iOS 13.0, if the app is written in SwiftUI like in my case

@onevcat
Copy link
Owner

onevcat commented Oct 1, 2021

@andrei115 For SwiftUI support, it is the planned dropping of iOS 13 support (and starting from iOS 14) since we need to use @StateObject to make the image loading logic correctly following SwiftUI design pattern. SwiftUI on iOS 13 is so broken and brings very heavy maintenance burden.

@andrei115
Copy link

@onevcat I know, but still...I am not able to get away with not supporting ios 13 for a production grade app, considering it accounts to about 8% of user base.
Fortunately, I managed to solve this by copying Kingfisher 6.3 source code in my app and it seems to work fine.

@onevcat
Copy link
Owner

onevcat commented Oct 3, 2021

@andrei115
Wow, that's nice! Thanks for the feedback. Really wish Apple could fix this in the toolchain :(

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

6 participants