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 #35

Open
ZabirTarique opened this issue Jun 13, 2021 · 4 comments
Open

Version solving failed #35

ZabirTarique opened this issue Jun 13, 2021 · 4 comments

Comments

@ZabirTarique
Copy link

ZabirTarique commented Jun 13, 2021

hello,
I am developing an application, which contains this libraries-

dependencies:
flutter:
sdk: flutter
bloc: ^6.0.3
flutter_bloc: ^6.0.6
equatable: ^1.0.2
cupertino_icons: ^1.0.2
buttons_tabbar: ^1.2.1
tab_indicator_styler: ^2.0.0-null-safety
contained_tab_bar_view: ^0.7.1
speech_recognition: ^0.3.0+1
table_calendar: ^3.0.0
flutter_week_view: ^1.1.0
md2_tab_indicator: ^1.0.2
expandable: ^5.0.1
google_maps_flutter: ^2.0.3
http: ^0.12.2
encrypt: ^4.1.0
file_picker: ^3.0.1
archive: ^2.0.13
path_provider:
url_launcher:
pbkdf2_dart: ^2.1.0
dio: ^3.0.10
aes_crypt: ^0.1.1
intl: ^0.17.0
global_configuration: ^1.6.0
imei_plugin: ^1.2.0
device_info: ^2.0.0
sqflite: ^2.0.0+3
screenshot: ^0.3.0
camerawesome: ^0.2.2
path:
video_player:
shared_preferences: ^2.0.6
speech_to_text: ^4.2.1
image_editor_pro: ^1.1.8

while I import image_editor_pro: ^1.1.8 in the yaml file it seems something like this-
Because image_editor_pro >=1.1.0 depends on dio ^4.0.0 and test_app depends on dio ^3.0.10, image_editor_pro >=1.1.0 is forbidden.
So, because test_app depends on image_editor_pro ^1.1.8, version solving failed.
pub get failed (1; So, because test_app depends on image_editor_pro ^1.1.8, version solving failed.)

how can I fix this error. I need to use image editor in my app. Is there any way to solve this issue?
Thank you in advance.

I am adding some screenshot here.
1
2
4

@AshfaqAshi
Copy link

Yes, it uses old versions of dependencies and version solving fails if we use new versions of those packages

@ZabirTarique
Copy link
Author

Thanks for your information. Can you please tell me is there any way to resolve it?

@bensal-kb
Copy link

Not from your side, the package should be updated to a new version.

@ZabirTarique
Copy link
Author

Not from your side, the package should be updated to a new version.

Thanks a lot.

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