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

why intl always resolve failed. #2409

Closed
1 task done
parcool opened this issue Dec 6, 2024 · 3 comments · Fixed by #2416
Closed
1 task done

why intl always resolve failed. #2409

parcool opened this issue Dec 6, 2024 · 3 comments · Fixed by #2416
Labels
question Further information is requested

Comments

@parcool
Copy link

parcool commented Dec 6, 2024

Is there an existing issue for this?

The question

Why doesn't flutter_quill update its intl package dependency? It causes version conflicts. I noticed flutter_quill is using an intl package version from a year ago, even though flutter_quill itself maintains very active updates.

/Users/xxx/Flutter/SDK/bin/flutter --no-color pub get
Resolving dependencies...
Because flutter_quill 10.8.5 depends on intl ^0.19.0 and no versions of flutter_quill match >10.8.5 <11.0.0, flutter_quill ^10.8.5 requires intl ^0.19.0.
So, because xxx depends on both intl ^0.20.1 and flutter_quill ^10.8.5, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on intl: flutter pub add intl:^0.19.0
Process finished with exit code 1
image
@parcool parcool added the question Further information is requested label Dec 6, 2024
@parcool parcool closed this as completed Dec 6, 2024
@parcool
Copy link
Author

parcool commented Dec 6, 2024

I apologize, my memory is a bit fuzzy.

@EchoEllet
Copy link
Collaborator

Why doesn't flutter_quill update its intl package dependency?

The versions in pubspec.yaml contain the minimum required versions, not the versions that will be used in your project (pubspec.lock).

It causes version conflicts

Requiring newer versions will cause conflicts, too, especially with projects that use an older version of Dart.

The version 0.20.0 is not breaking. We can update the version constraint if needed.

Could you explain what the issue was?

@EchoEllet
Copy link
Collaborator

Fixed by #2416

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants