android - 如何在没有 Identity Toolkit API 的情况下使 Firebase 身份验证完全工作

Question

我正在尝试在 Android 项目中使用 Firebase 创建电子邮件密码帐户。我使用 Android Studio 的 Firebase 助手添加了 Firebase。

创建用户代码如下。

mAuth.createUserWithEmailAndPassword(email, password)
            .addOnCompleteListener(this, new OnCompleteListener<AuthResult>() {
                @Override
                public void onComplete(@NonNull Task<AuthResult> task) {
                        if (task.isSuccessful()) {
                            FirebaseUser user = mAuth.getCurrentUser();
                            onLoginUpdateUI(user);
                        } else {
                            System.err.println("message:\n" + task.getException().getMessage());
                            onLoginUpdateUI(null);
                        }
                }
            });

我输入了有效的电子邮件和密码(超过 6 个字符)我收到以下错误:

com.google.firebase.FirebaseException: An internal error has occurred. [ Identity Toolkit API has not been used in project before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/identitytoolkit.googleapis.com/overview?project= then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry. ]

我在 https://console.firebase.google.com 中启用了电子邮件/密码登录方法.

然后我去了https://console.developers.google.com并启用了 Identity Toolkit API。

然后身份验证工作正常。

但是我见过

The newest version of Google Identity Toolkit has been released as Firebase Authentication. Going forward, feature work on Identity Toolkit will be frozen and all new feature development will be done on Firebase Authentication. We encourage Identity Toolkit developers to move to Firebase Authentication as soon as is practical for their applications; however, Identity Toolkit continues to work and will not be deprecated without a further announcement.

所以我的问题是，如果他们打算弃用 Identity Toolkit API，如何在没有 Identity Toolkit API 的情况下完全进行 Firebase 电子邮件/密码身份验证？

Answer 1

我必须在 https://console.firebase.google.com 中手动创建一个新的 Firebase 项目(不使用 Android Studio 中的 Firebase 帮助)并将 google-services.json 替换为新的。它奏效了。