-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Cocoapods's pods that depend on PromiseKit 6.22.1+ fail to pod lib lint
while using Xcode 14.3
#1317
Comments
Hello @crsantos |
I can, of course, if you agree. Let me just remind you that this will drop PromiseKit for any deployment target under iOS 11. Hold my 🍺 |
8 is very old now. All the same this feels like a CocoaPods bug. It should update deployment targets based on the build environment. We support back to 8, but don't care if it moves forwards. Maybe our podspec is wrong? As said though iOS 8 is super old so there's no way this will cause anyone difficulty. 11 is also old. So sure. |
well I disagree, CocoaPods shouldn't require us to update our oldest supported deployment target. it generates xcodeprojects. But I dunno if they've looked this deep. I'm not saying it's a bug because I won't apply this patch, but you are not seeing my point I think in that it is up to CocoaPods to make this shit work. Putting the onus on us is one layer incorrectly applied. Like, I've done my fair sure of packaging projects lol |
That is definitely true 😄 And I absolutely get your point, we shouldn't need to worry about this, but I'm just not sure if Cocoapods could fix that as the main issue was happening with Xcode itself 😞 |
Version: 6.22.1
Installed via: Cocoapods
Hi,
I'm following up after this issue #1308 and the PR that fixed it: #1311.
That PR fixed Xcode 14.3 builds, but while using Cocoapods, as you said on the issue, it creates a temporary project for the linting process, based on the
podspec
.Any pod that depends on PromiseKit will fail on linting due to the iOS 8.0 deployment target.
I know you referred here that dropping support for older versions is tricky, #1311 (comment)
But this also blocks people from using Xcode 14.3 and beyond, hence my question:
are we good to also bump the podspec's deployment target to
11.0
?(Same as #1311 did for the xcodeproj)
Log
This can be replicated with a simple
pod lib lint
on the repo:Expand
The text was updated successfully, but these errors were encountered: