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

Update flutter_keyboard_visibility to 6.0.0 #34

Open
alod2019 opened this issue Feb 18, 2024 · 1 comment · May be fixed by #35
Open

Update flutter_keyboard_visibility to 6.0.0 #34

alod2019 opened this issue Feb 18, 2024 · 1 comment · May be fixed by #35

Comments

@alod2019
Copy link

If flutter_keyboard_visibility dependency is also used in a project it's latest version fails to resolve

Because keyboard_attachable 2.2.0 depends on flutter_keyboard_visibility ^5.4.1 and ib depends on flutter_keyboard_visibility 6.0.0, keyboard_attachable 2.2.0 is forbidden.
So, because ib depends on keyboard_attachable 2.2.0, version solving failed.
@stephane-couget
Copy link

Hi Everyone,

First congratulations on your magnificent work.

As Keyboard_attachable ^2.2.0 depends exclusively on flutter_keyboard_visibility version 5.4.1, when I want to update flutter_typeahead version 5.0.1. In 5.2.0, I get a dependency error:

Because keyboard_attachable >=2.2.0 depends on flutter_keyboard_visibility ^5.4.1 and TDC_RapVerif depends on flutter_keyboard_visibility ^6.0.0, keyboard_attachable >=2.2.0 is forbidden. So, because TDC_RapVerif depends on keyboard_attachable ^2.2.0, version solving failed. Process finished with exit code 1

Because flutter_typeahead >=5.0.2 depends on flutter_keyboard_visibility ^6.0.0 and TDC_RapVerif depends on flutter_keyboard_visibility ^5.4.1, flutter_typeahead >=5.0.2 is forbidden. So, because TDC_RapVerif depends on flutter_typeahead ^5.2.0, version solving failed. You can try the following suggestion to make the pubspec resolve: * Consider downgrading your constraint on flutter_typeahead: flutter pub add flutter_typeahead:^5.0.1 In short, I'm stuck!

Thank you for any help in finding a way out of this well.

Sincerely,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants