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

Version solving failed #34

Open
nima-dvlp opened this issue May 15, 2022 · 2 comments · May be fixed by #39
Open

Version solving failed #34

nima-dvlp opened this issue May 15, 2022 · 2 comments · May be fixed by #39
Assignees

Comments

@nima-dvlp
Copy link

Adding these lines to pubspec.yaml like this, will be fail result of the flutter pub get.

dependencies:
  tus_client: ^1.0.2
  tus_client_file_store: ^0.0.3
$ flutter pub get
Because tus_client_file_store >=0.0.3 depends on tus_client ^0.1.1 and prj depends on tus_client ^1.0.2, tus_client_file_store >=0.0.3 is forbidden.
So, because prj depends on tus_client_file_store ^0.0.3, version solving failed.
Running "flutter pub get" in prj...                                   
pub get failed (1; So, because prj depends on tus_client_file_store ^0.0.3, version solving failed.)

Even with flutter pub add the result is the same 🤔 :

$ flutter pub add tus_client
.
.
.
+ tus_client 1.0.2
.
.
.
$ flutter pub add tus_client_file_store
Because tus_client_file_store >=0.0.3 depends on tus_client ^0.1.1 and tus_client_file_store <0.0.3 depends on tus_client ^0.0.4, every version of tus_client_file_store requires tus_client ^0.0.4 or ^0.1.1.
So, because prj depends on both tus_client ^1.0.2 and tus_client_file_store any, version solving failed.
@hyperov
Copy link

hyperov commented Oct 20, 2022

I'm having the same issue

@elsandner
Copy link

same

@jjmutumi jjmutumi self-assigned this Oct 17, 2023
@jjmutumi jjmutumi linked a pull request Oct 17, 2023 that will close this issue
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

Successfully merging a pull request may close this issue.

4 participants