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

Package fails because of unresolved dependencies #13

Closed
pph7 opened this issue Jan 13, 2021 · 3 comments
Closed

Package fails because of unresolved dependencies #13

pph7 opened this issue Jan 13, 2021 · 3 comments

Comments

@pph7
Copy link

pph7 commented Jan 13, 2021

In my current project, dart-package-analyzer always fails on the

flutter pub upgrade

command with the following error message:

ERR: Because every version of flutter_localizations from sdk depends on intl 0.17.0-nullsafety.2 and firebase_auth_web >=0.3.0-dev.1 depends on intl ^0.16.1, flutter_localizations from sdk is incompatible with firebase_auth_web >=0.3.0-dev.1.
 And because firebase_auth >=0.20.0 depends on firebase_auth_web ^0.3.2+6, flutter_localizations from sdk is incompatible with firebase_auth >=0.20.0.
 So, because repeat_native depends on both firebase_auth ^0.20.0 and flutter_localizations any from sdk, version solving failed.

See also: flutter/flutter#71801

Locally this command runs without a problem. On idea is that the package analyzer uses the beta channel while we are using the stable channel.

Possible solution: Add a configuration option where we can choose which version of flutter to use.

@pph7
Copy link
Author

pph7 commented Jan 13, 2021

I just confirmed that this problem does not occur in v2 of the package analyzer.

@axel-op
Copy link
Owner

axel-op commented Jan 20, 2021

Hi,

Thanks for the issue. As you guessed, this will be automatically resolved once the firebase_auth_web will be updated. The reason why I've set the Flutter channel on beta is to maintain compatibility with libraries that have opted in null safety (see #11).

I just confirmed that this problem does not occur in v2 of the package analyzer.

I don't recommend using v2, because it uses an old version of Pana that is not updated anymore.

Possible solution: Add a configuration option where we can choose which version of flutter to use.

See #5 to use a different Flutter channel with this action.

@axel-op
Copy link
Owner

axel-op commented Feb 3, 2021

I think that this has been solved with firebase/flutterfire@1e8f48a.

@axel-op axel-op closed this as completed Feb 3, 2021
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