Repository navigation
Won't build with Carthage and Xcode 14.3 #358
Description
New Issue Checklist
- [X ] I have tried with the latest version of OHHTTPStubs
- [X ] I have read the README
- [X ] I have read the Using the right Swift Version of
OHHTTPStubsfor your project section - [X ] I have searched in the existing issues
- [X ] I have read the OHHTTPStubs wiki to see if there wasn't a detailed page talking about my issue
Environment
- version of OHHTTPStubs: 9.1.0
- integration method you are using:
- Cocoapods
- [ X] Carthage
- submodule
- other
- version of the tool you use: 0.38.0
Issue Description
Library will not build using Xcode version 14.3. The error is related to the deployment target being set to 8.0, where the minimum for Xcode 14.3 is 11.
Complete output when you encounter the issue (if any)
Reacted by Artur Jankowski
Activity
dazzli commentedon Jun 1, 2023
The same at my project! Please update a bit this beauty
chore: change OHHTTPStubs dependency from carthage to SPM
kishorepran commentedon Jul 15, 2023
@electricalen , @dazzli , similar issue here,
I guess the workaround is to use Xcode 14.2 or below. OR raise a pr which fixes this for carthage + SPM + cocoapods.
We have have few pr already in pipeline for this issue but none of them address the concerns for all the 3
kishorepran commentedon Jul 15, 2023
Hi @jeffctown , are there any plans to update the pod spec to 9.0 as well...? Is it okay to submit a pr as done for SPM here thanks.
I would love to collaborate and help maintain this repo.
CC: @AliSoftware / @Liquidsoul
ryukukimura commentedon Oct 24, 2023
I have the same problem.
I would like to continue using OHHTTPStubs in Xcode 14.3.1 as well.
Liquidsoul commentedon Oct 25, 2023
Thank you all for your patience, I'll try to see if I can fix this 🙇
See my comment here : #361 (comment)
adamsousa commentedon Jan 10, 2024
Any updates on this?
AliSoftware commentedon Jan 11, 2024
Sorry for the very long delay on this, I've been away from OSS for quite a long time and I know that have caused this to stale for way too long.
I've commented in #361 (comment). TL;DR we'll need that PR to be finalized with
.podspecupdates (or have @Liquidsoul create a PR for his branch already containing the necessary changes) and then I'll be able to land the PR.