[firebase_auth] 6.7.0 requires platform interface 9.1.0 but allows 9.0.7
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- mobile-dev
Research direction
Open packages/firebase_auth/firebase_auth/pubspec.yaml and inspect the firebase_auth_platform_interface constraint. Reproduce with flutter pub get and compilation using firebase_auth 6.7.0 with platform interface 9.0.7; done means the lower bound requires an interface version that provides migrateCurrentUser and the app compiles without a direct platform-interface dependency.
Written by the indexing model from the issue text.
Description
Bug report
When an app upgrades to firebase_auth 6.7.0 while its lockfile retains firebase_auth_platform_interface 9.0.7, compilation fails because Auth calls a named argument that the selected interface does not define.
Reproducing the issue
- Create a Flutter app with
firebase_auth: ^6.7.0. - Keep or pin the lockfile selection to
firebase_auth_platform_interface 9.0.7(the lower bound currently allowed by the package). - Run
flutter pub get, then compile the app.
Observed dependency output and error:
firebase_auth_platform_interface 9.0.7 (9.1.0 available)
firebase_auth-6.7.0/lib/src/firebase_auth.dart:416:7:
Error: No named parameter with the name 'migrateCurrentUser'.
Expected behavior
The dependency solver should select a platform interface version that provides every API used by firebase_auth 6.7.0, without requiring applications to directly depend on the internal platform interface package.
Cause and workaround
firebase_auth 6.7.0 declares firebase_auth_platform_interface: ^9.0.7, but migrateCurrentUser was introduced in firebase_auth_platform_interface 9.1.0. Adding firebase_auth_platform_interface: ^9.1.0 directly to the application resolves the compile error.
Proposed fix
Raise the firebase_auth_platform_interface lower bound in packages/firebase_auth/firebase_auth/pubspec.yaml from ^9.0.7 to ^9.1.0.
- Dominant language
- Dart
- Stars
- 9.3k
- Forks
- 4.1k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 34
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from firebase/flutterfire
-
Needs Attention platform: ios plugin: crashlytics type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
firebase/flutterfire#18722 · 3 comments ·
Maintainers usually reply within 1 day
-
Needs Attention platform: windows plugin: ai type: documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
firebase/flutterfire#18720 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
firebase/flutterfire#18728 ·
Maintainers usually reply within 1 day
-
[cloud_firestore]: a snapshots() listener cancelled while it registers is never removed nativelyOpen
Difficulty 3/5 1-2 days Newbie friendliness 72/100
firebase/flutterfire#18724 ·
Maintainers usually reply within 1 day
-
Needs Attention platform: ios platform: macos plugin: app_check reproduced type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
firebase/flutterfire#18718 · 1 comment ·
Maintainers usually reply within 1 day
All issues in firebase/flutterfire
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jiangtian616/JHenTai#833 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
decentespresso/decaid#913 ·
Maintainers usually reply within 1 day