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

The package dependency graph can not be resolved #289

Open
pitt500 opened this issue Jan 30, 2020 · 3 comments
Open

The package dependency graph can not be resolved #289

pitt500 opened this issue Jan 30, 2020 · 3 comments

Comments

@pitt500
Copy link

pitt500 commented Jan 30, 2020

Hello,

Today I tried to add DateTools through Swift package manager in Xcode 11.3 and I got this error:

image

The package dependency graph can not be resolved; unable find any available tag for the following requirements:

https://github.com/MatthewYork/DateTools.git — 4.0.0..<5.0.0

My only way to make it work is by adding it manually (without using cocoapods), but I wonder if there is something wrong with my side that I could do to fix this issue or in fact, the library has a bug with SPM.

Thanks.

@MatthewYork
Copy link
Owner

SPM support will be available soon. It is currently using Swift 3 tooling and most likely incompatible with whatever you are doing now.

I have been on a very long hiatus, but have returned and would like to get DateTools current. I assume there will be a pull request soon, which I will certainly merge.

@pitt500
Copy link
Author

pitt500 commented Feb 2, 2020

Ok, let me check if I can help you upgrade to swift 5 and/or SPM support. Thanks for your response @MatthewYork

@prabh-62
Copy link

prabh-62 commented Feb 8, 2021

I tried adding DateTools via Swift Package Manager (Xcode 12.4) today

dateTools_SPM_5

and I received an error:

Package Resolution Failed

"DateTools" could not be resolved

because DateTools >=2.0.0 contains incompatible tools version and root depends on DateTools 5.0.0..<6.0.0, version solving failed.

dateTools_SPM_error

I see there are some open pull requests which aim to fix this issue. I can open a Pull request if none of the open pull requests addressing this issue are going to get merged.

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

3 participants