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 support for provider ^4.0.0 #9

Closed
charkala opened this issue Dec 30, 2019 · 4 comments · Fixed by #10
Closed

Update support for provider ^4.0.0 #9

charkala opened this issue Dec 30, 2019 · 4 comments · Fixed by #10

Comments

@charkala
Copy link

Hi @ayalma

flutter_bloc v3.0.0 is out and uses provider ^4.0.0 and apparently feature_discovery ^0.6.0 is not compatible with the new version.

I've currently rolled back to flutter_bloc v2 as a workaround for now.

Running "flutter pub get" in my_app...
Because flutter_bloc >=3.0.0 depends on provider ^4.0.0 and feature_discovery 0.6.0 depends on provider ^3.1.0, flutter_bloc >=3.0.0 is incompatible with feature_discovery 0.6.0.
And because no versions of feature_discovery match >0.6.0 <0.7.0, flutter_bloc >=3.0.0 is incompatible with feature_discovery ^0.6.0.
So, because my_app depends on both feature_discovery ^0.6.0 and flutter_bloc ^3.0.0, version solving failed.
pub get failed (1; So, because my_app depends on both feature_discovery ^0.6.0 and flutter_bloc ^3.0.0, version solving failed.)
Exited (1)

Thank you.

@charkala charkala changed the title Update support for provider ^4.0.0 Update support for provider ^4.0.0 Dec 30, 2019
@axel-op
Copy link
Contributor

axel-op commented Dec 30, 2019

I made a pull request from my fork to fix this: #10 😊

@ayalma ayalma closed this as completed in #10 Jan 1, 2020
@charkala
Copy link
Author

charkala commented Jan 7, 2020

@ayalma when do you expect to publish the update?

@ayalma
Copy link
Owner

ayalma commented Jan 19, 2020

Sorry for being late @charkala
I published it

@charkala
Copy link
Author

@ayalma no worries. thank you for providing this feature.

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.

3 participants