Ionic 3/AngularFire2 authState在Android端不持久化（Web端正常）

Hey there, I’ve dealt with this exact issue before—auth persistence working on web but breaking on Android is a super common gotcha with Ionic and Firebase. Let’s walk through the most likely fixes step by step:

1. Explicitly Set Firebase Auth Persistence After Platform Ready #

The biggest culprit here is usually that Firebase’s auth persistence isn’t being configured correctly on Android, especially if you’re subscribing to authState before the Ionic platform is fully ready. Mobile devices need a moment to initialize storage systems, so wrap your persistence setup and authState subscription inside platform.ready():

constructor(
  private platform: Platform,
  private statusBar: StatusBar,
  private splashScreen: SplashScreen,
  private afAuth: AngularFireAuth
) {
  this.platform.ready().then(() => {
    // Set persistence to LOCAL first
    this.afAuth.auth.setPersistence(firebase.auth.Auth.Persistence.LOCAL)
      .then(() => {
        console.log("Successfully set auth persistence to LOCAL");
        // Now subscribe to authState
        this.afAuth.authState.subscribe(user => {
          if (user) {
            this.rootPage = "TabsPage";
            console.log("User logged in:", JSON.stringify(user));
          } else {
            this.rootPage = "LoginPage";
            console.log("No active user session");
          }
        });
      })
      .catch(err => {
        console.error("Failed to set persistence:", err);
      });

    // Other platform init tasks
    this.statusBar.styleDefault();
    this.splashScreen.hide();
  });
}

Why this works: platform.ready() ensures all native plugins (including Firebase’s storage layer for auth persistence) are loaded before we try to access or set user session data.

2. Verify Android Permissions & Firebase Config #

• Check Internet Permission: Make sure AndroidManifest.xml (in android/app/src/main/) includes the internet permission (Ionic usually adds this by default, but double-check):

  <uses-permission android:name="android.permission.INTERNET" />
  

• Validate google-services.json: Confirm this file is placed correctly in android/app/ and matches the config from your Firebase project console. A mismatched project ID or API key can silently break auth persistence.

3. Clear App Data & Reinstall #

Sometimes stale cached data or corrupted session storage can cause persistence issues. Uninstall the app from your Android device/emulator, clear any leftover data, then rebuild and reinstall the app with:

ionic cordova build android --prod

4. Check Dependency Version Compatibility #

Ionic 3 requires specific versions of AngularFire2 and Firebase to work properly. Mismatched versions can lead to unexpected behavior on mobile. Verify your package.json has compatible dependencies (example working versions):

"angularfire2": "^5.0.2",
"firebase": "^5.12.0",
"@angular/core": "^5.2.11"

If your versions are way off, try downgrading/upgrading to these compatible releases.

Final Notes #

If none of the above fixes work, enable Firebase debug logging on Android to get more detailed error messages:

firebase.database.enableLogging(true);

This will print auth-related logs to your Android studio console, which can help pinpoint exactly where the persistence is failing.

内容的提问来源于stack exchange，提问作者rhysclay