Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[firebase_auth_web]: authStateChanges() never emits in --profile web builds (listener key 'no-op' collides)

Chiusa
  • Qualcosa non va?
#18,728 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
72/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
dart
Ambito
authentication, web-dev

Direzione di ricerca

Start with packages/firebase_auth/firebase_auth_web/lib/src/interop/auth.dart and packages/firebase_core/firebase_core_web/lib/src/interop/utils/utils.dart, focusing on _authStateWindowsKey(), _idTokenStateWindowsKey(), and the listener storage methods. Reproduce with a Flutter web app using flutter build web --profile and multiple auth streams. Done means authStateChanges() emits its initial state in profile builds without cancelling another listener, while debug and release behavior remains intact.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Is there an existing issue for this?
  • I have searched the existing issues.
Which plugins are affected?

Auth, Core

Which platforms are affected?

Web

Description

In a flutter build web --profile build, FirebaseAuth.instance.authStateChanges() never emits. An app that waits for the first auth event (for example a router redirect that holds a splash screen until auth state is known) hangs forever. Debug and release builds work.

The JS SDK itself is fine. In the same page, onAuthStateChanged called directly through the JS SDK fires immediately with null.

Cause. The two packages disagree about what "debug" means:

  • firebase_auth_web builds the hot-restart listener key only under Flutter's kDebugMode. kDebugMode is false in profile, so every listener gets the same key, 'no-op':
    packages/firebase_auth/firebase_auth_web/lib/src/interop/auth.dart, _authStateWindowsKey() / _idTokenStateWindowsKey(): 
    if (kDebugMode) { ... return '$key-${_authStateListeners[key]}'; }
return 'no-op';
  • firebase_core_web stores and cancels those listeners under its own flag, which is true in profile:
    packages/firebase_core/firebase_core_web/lib/src/interop/utils/utils.dart: 
    const bool _kDebugMode = !bool.fromEnvironment('dart.vm.product');
    setWindowsListener / unsubscribeWindowsListener / removeWindowsListener are all gated on it.

So in profile, onAuthStateChanged / onIdTokenChanged store their JS unsubscribe function at window['no-op']. The next getter call runs unsubscribeWindowsListener('no-op'), which calls that stored function and cancels the previous subscription's JS listener. The Dart StreamController stays open but never receives an event. The event it seeded with _changeController!.add(_initUser) was added before any listener existed, so the broadcast controller dropped it.

In release both flags are false, and in debug both are true with unique keys, which is why only profile is affected.

The code is unchanged on main as of today.

Suggested fix: use the same condition in both places. For example, have firebase_core_web use kDebugMode from package:flutter/foundation.dart, or make _authStateWindowsKey() / _idTokenStateWindowsKey() always return a unique key.

Reproducing the issue
  1. Take any web app that listens to FirebaseAuth.instance.authStateChanges() and also triggers a second auth stream (idTokenChanges(), userChanges(), or a second authStateChanges() call).
  2. flutter build web --profile and serve build/web.
  3. Open it signed out. The authStateChanges() listener never fires. With flutter run -d chrome or flutter build web --release, it fires null straight away.

To confirm it is the listener being cancelled, put prints in the stream: the provider builds and the redirect runs with the state still loading, but no event ever arrives. In the same page, firebase_auth.onAuthStateChanged(getAuth(app), cb) from the JS SDK fires at once.

Firebase Core version

4.15.0 (firebase_core_web 3.12.0)

Flutter Version

3.47.2

Relevant Log Output
No error is logged. The auth stream is silently cancelled.
Flutter dependencies
firebase_core: 4.15.0
firebase_core_web: 3.12.0
firebase_auth: 6.7.0
firebase_auth_web: 6.3.0
Additional context and comments

Found while profiling a production app. The fix above is based on reading the source, and the diagnosis was confirmed with print statements in a profile build. I have not built a standalone minimal repro project.

Lingua principale
Dart
Stelle
9.3k
Fork
4.1k
Merge medio
2g 6h
PR unite (30g)
38

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di firebase/flutterfire

Tutte le issue di firebase/flutterfire

Issue simili

Altre issue su Dart

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.