You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Supported per-app boundary between initial persisted-user projection and pending Auth recovery on Android / FlutterFire
#18976
We are reviewing a fail-closed startup integration using these locally
pinned versions: Firebase Auth Android 24.2.0, FlutterFire firebase_auth
6.5.6, firebase_auth_platform_interface 9.0.5, firebase_core 4.13.0 and
firebase_core_platform_interface 8.1.0. We are not requesting a private
storage format, reflection-based access or an unsupported API.
The Flutter user-management documentation describes an initial Auth event
after persisted local credentials have been restored. The Android
getPendingAuthResult contract describes a recovered web sign-in after an
Activity is reclaimed. We understand those to be different scopes and
are not treating an initial null user, an elapsed timeout or a null
pending-result getter as a general completion barrier.
Could you clarify the supported guarantees for the following questions?
For one exact FirebaseApp/FirebaseAuth instance, which public signal
establishes completion of the persisted-current-user initialization?
Which operations, if any, may still be pending when that signal fires?
Is there a supported per-app barrier covering startup-recovered provider
operations and relevant reCAPTCHA-related recovery that can change the
admitted session? We are not asking for all background token work to
cease forever. Alternatively, must applications track
only their explicitly initiated tasks and react to later state changes?
Can the initial AuthStateListener callback occur while the task exposed
by getPendingAuthResult is incomplete? If so, what is the recommended
ordering for an explicit new email/password operation without racing
a recovered operation from that app's previous process?
In the pinned FlutterFire implementation, Android suppresses the first
Auth listener callback, while Dart authStateChanges initially yields
the delegate's currentUser from Core plugin constants. If Auth is
attached only after a native App Check confirmation, is delaying the
first Dart Firebase.initializeApp until after that attachment a
supported way to obtain the standard initial-user projection? Are
there lifecycle or initialization constraints we should account for?
If Dart Core was already initialized before Auth attachment, is there
a public refresh path without sign-in, app deletion or internal-cache
manipulation?
If a global idle guarantee is not part of the supported API contract,
please confirm its scope rather than suggesting that a null getter or
agreement of two cached snapshots proves global inactivity.
Is there a supported positive signal that the Dart Auth listener
registrations are ready on the pinned Android engine/messenger?
We do not treat an initial cached user or a private disposal wait as
such a signal. We have seen authStateReady() in the JavaScript Auth
reference and are not assuming it exists in Android or Flutter.
We have no real-user data to attach. Any follow-up reproduction would be
separately reviewed, minimal and synthetic, and would describe its exact
preconditions rather than claim that a simulated task proves a public
initialization guarantee.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
We are reviewing a fail-closed startup integration using these locally
pinned versions: Firebase Auth Android 24.2.0, FlutterFire firebase_auth
6.5.6, firebase_auth_platform_interface 9.0.5, firebase_core 4.13.0 and
firebase_core_platform_interface 8.1.0. We are not requesting a private
storage format, reflection-based access or an unsupported API.
The Flutter user-management documentation describes an initial Auth event
after persisted local credentials have been restored. The Android
getPendingAuthResult contract describes a recovered web sign-in after an
Activity is reclaimed. We understand those to be different scopes and
are not treating an initial null user, an elapsed timeout or a null
pending-result getter as a general completion barrier.
Could you clarify the supported guarantees for the following questions?
establishes completion of the persisted-current-user initialization?
Which operations, if any, may still be pending when that signal fires?
operations and relevant reCAPTCHA-related recovery that can change the
admitted session? We are not asking for all background token work to
cease forever. Alternatively, must applications track
only their explicitly initiated tasks and react to later state changes?
by getPendingAuthResult is incomplete? If so, what is the recommended
ordering for an explicit new email/password operation without racing
a recovered operation from that app's previous process?
Auth listener callback, while Dart authStateChanges initially yields
the delegate's currentUser from Core plugin constants. If Auth is
attached only after a native App Check confirmation, is delaying the
first Dart Firebase.initializeApp until after that attachment a
supported way to obtain the standard initial-user projection? Are
there lifecycle or initialization constraints we should account for?
If Dart Core was already initialized before Auth attachment, is there
a public refresh path without sign-in, app deletion or internal-cache
manipulation?
please confirm its scope rather than suggesting that a null getter or
agreement of two cached snapshots proves global inactivity.
registrations are ready on the pinned Android engine/messenger?
We do not treat an initial cached user or a private disposal wait as
such a signal. We have seen
authStateReady()in the JavaScript Authreference and are not assuming it exists in Android or Flutter.
We have no real-user data to attach. Any follow-up reproduction would be
separately reviewed, minimal and synthetic, and would describe its exact
preconditions rather than claim that a simulated task proves a public
initialization guarantee.
References
All reactions