Firebase创建用户避免自动登录：空安全迁移后异常求助

核心问题点 #

• 重复初始化同名FirebaseApp：空安全启用后，重复调用Firebase.initializeApp创建同名App会直接抛出异常，导致secondaryApp创建失败，后续逻辑 fallback 到默认Auth实例，引发自动登录问题。
• then回调无返回值导致credential为null：原代码中createUserWithEmailAndPassword后的then未返回结果，使得credential始终为null，后续的邮件验证逻辑完全失效，且空安全下这种空值处理会引发潜在问题。
• 资源清理不严谨：原代码中仅在正常流程下删除secondaryApp，若中间抛出异常，App实例会残留，导致后续重复初始化时持续报错。

修复后的完整代码 #

Future<bool> signUpUser(String username, String email, String password,
    String firstName, String lastName, String? birthday, String? gender) async {
  _status = Status.Authenticating;
  notifyListeners();

  FirebaseApp? secondaryApp;
  try {
    // 先检查是否已存在同名App，避免重复初始化
    secondaryApp = Firebase.app('Secondary');
  } catch (_) {
    // 不存在则创建新的App实例
    secondaryApp = await Firebase.initializeApp(
      name: 'Secondary',
      options: Firebase.app().options,
    );
  }

  try {
    // 改用await替代then，确保获取到正确的UserCredential
    final auth = FirebaseAuth.instanceFor(app: secondaryApp);
    final credential = await auth.createUserWithEmailAndPassword(
      email: email,
      password: password,
    );

    // 创建用户数据到数据库
    await _userServices.createUser(
      uid: credential.user!.uid,
      username: username,
      email: email,
      firstName: firstName,
      lastName: lastName,
      birthday: birthday,
      gender: gender,
      status: 'aktiv',
      role: 'User',
    );

    // 发送验证邮件，先判断user是否存在再执行
    if (credential.user != null) {
      await credential.user!.sendEmailVerification();
    }

    print('用户创建完成');
    _status = Status.Unauthenticated;
    notifyListeners();
    return true;
  } on FirebaseAuthException catch (e) {
    print('Auth错误: ${e.message}');
    _status = Status.Unauthenticated;
    notifyListeners();
    return false;
  } catch (e) {
    print('未知错误: ${e.toString()}');
    _status = Status.Unauthenticated;
    notifyListeners();
    return false;
  } finally {
    // 无论成功失败，都确保删除secondaryApp，避免实例残留
    if (secondaryApp != null) {
      await secondaryApp.delete();
      print('Secondary App已删除');
    }
  }
}

额外说明 #

• 用try-catch检查App实例是否存在，避免重复初始化的异常；
• 替换then为await，让代码逻辑更线性，同时保证credential能正确获取到值；
• 将secondaryApp的删除逻辑放在finally块中，确保资源一定会被清理；
• 增加了对credential.user的非空判断，避免空安全下的强制解空风险。

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