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

Potential Conflict: flutter_secure_storage (9.2.2) and flutter_sound (9.17.0) #826

Open
yanaico opened this issue Nov 18, 2024 · 1 comment

Comments

@yanaico
Copy link

yanaico commented Nov 18, 2024

I'm encountering potential conflicts between the flutter_sound (version 9.17.0) and flutter_secure_storage (version 9.2.2) packages in my Flutter application.

Can you please fix this issue?

Issue description:
Because no versions of flutter_secure_storage match >9.2.2 <10.0.0 and flutter_secure_storage 9.2.2 depends on flutter_secure_storage_web ^1.2.1, flutter_secure_storage ^9.2.2 requires flutter_secure_storage_web ^1.2.1.
And because no versions of flutter_secure_storage_web match >1.2.1 <2.0.0 and flutter_secure_storage_web 1.2.1 depends on js ^0.6.3, flutter_secure_storage ^9.2.2 requires js ^0.6.3.
And because flutter_sound >=9.17.0 depends on flutter_sound_web 9.17.0 which depends on js ^0.7.1, flutter_secure_storage ^9.2.2 is incompatible with flutter_sound >=9.17.0.
So, because be_pass depends on both flutter_sound ^9.17.0 and flutter_secure_storage ^9.2.2, version solving failed.

You can try one of the following suggestions to make the pubspec resolve:

Consider downgrading your constraint on flutter_secure_storage: flutter pub add flutter_secure_storage:^4.2.1
Consider downgrading your constraint on flutter_sound: flutter pub add flutter_sound:^9.6.0

@sandersaelmans
Copy link

Duplicate of #818

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

2 participants