Codelab: can not use firebase_auth_web

[tndevDE]

firebase_auth seems to be incompatible with firebase_ui_auth, as both require a different intl version as a dependency.

\Codelabs\firebase-get-to-know-flutter\step_02> flutter pub add firebase_auth_web
Because firebase_auth >=4.4.1 depends on firebase_auth_web ^5.3.1 which depends on intl ^0.17.0, firebase_auth >=4.4.1 requires intl ^0.17.0. And because every version of firebase_ui_auth depends on flutter_localizations from sdk which depends on intl 0.18.0, firebase_auth >=4.4.1 is incompatible with firebase_ui_auth. So, because gtk_flutter depends on both firebase_auth ^4.4.1 and firebase_ui_auth ^1.1.17, version solving failed.

[tndevDE]

I have switched to the stable version of flutter and now it works.

But in the description of "Codelab: Get to know Firebase for Flutter" it says you can also use the beta version.

You also need the following:

A browser of your choice, such as Google Chrome.
An IDE or text editor of your choice configured with the Dart and Flutter plugins, such as [Android Studio]> (https://developer.android.com/studio) or Visual Studio Code.
The latest stable version of Flutter or beta if you enjoy living on the edge.
A Google Account for the creation and management of your Firebase project.
The Firebase CLI logged in to your Google Account.

[darshankawar]

There's an open PR to update the intl version to latest: firebase/flutterfire#10317 which will possibly fix the issue.

For time being, you can use this solution.

Keeping this issue open for team's attention and to decide if anything need to be updated in respective codelab.

/cc @domesticmouse

[domesticmouse]

Thoughts @ericwindmill?

[ericwindmill]

This was a known issue with the Firebase for Flutter packages themselves. It was fixed recently. Please re-open and tag me if the problem comes up again.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.