Почему моя аутентификация входа в Google не работает в Android Studio? - PullRequest
Новая
       39

Почему моя аутентификация входа в Google не работает в Android Studio?

0 голосов
/ 07 апреля 2020

Поэтому я недавно добавил Google Войти, используя следующее руководство пользователя: https://developers.google.com/identity/sign-in/android/start-integrating

Я работаю с двумя другими участниками группы над этим проектом. Человек, который создал проект (в консоли Google), может использовать кнопку входа в систему очень хорошо. Тем не менее, оба моих товарища по команде и я получили код ошибки 12500 от Google. Я просмотрел stackoverflow и обнаружил, что у многих людей возникают такие же проблемы. Поэтому я последовал советам, данным этим людям, но безрезультатно Если бы кто-нибудь мог помочь мне понять, в чем моя проблема, это было бы очень признательно.

Ниже приведен мой код, связанный с Google Sign In, а также Logcat и сообщение об ошибке, которое я получаю, когда нажимаю кнопку «войти».

  1. Мой код 
import androidx.appcompat.app.AppCompatActivity;

import android.content.Intent;
import android.os.Bundle;
import android.util.Log;
import android.view.View;
import com.google.android.gms.auth.api.signin.GoogleSignIn;
import com.google.android.gms.auth.api.signin.GoogleSignInAccount;
import com.google.android.gms.auth.api.signin.GoogleSignInClient;
import com.google.android.gms.auth.api.signin.GoogleSignInOptions;
import com.google.android.gms.common.SignInButton;
import com.google.android.gms.common.api.ApiException;
import com.google.android.gms.tasks.Task;


public class MainActivity extends AppCompatActivity {

    SignInButton signin;
    int RC_SIGN_IN = 0;

    GoogleSignInClient mGoogleSignInClient;

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);

        signin = findViewById(R.id.sign_in_button);
        signin.setOnClickListener(new View.OnClickListener() {
            @Override
            public void onClick(View view) {
                switch (view.getId()) {
                    case R.id.sign_in_button:
                        signIn();
                        break;
                }
            }
        });

        GoogleSignInOptions gso = new GoogleSignInOptions.Builder(GoogleSignInOptions.DEFAULT_SIGN_IN)
                .requestEmail()
                .build();

        mGoogleSignInClient = GoogleSignIn.getClient(this, gso);
    }

    private void signIn() {
        Intent signInIntent = mGoogleSignInClient.getSignInIntent();
        startActivityForResult(signInIntent, RC_SIGN_IN);
    }

    @Override
    public void onActivityResult(int requestCode, int resultCode, Intent data) {
        super.onActivityResult(requestCode, resultCode, data);

        // Result returned from launching the Intent from GoogleSignInClient.getSignInIntent(...);
        if (requestCode == RC_SIGN_IN) {
            // The Task returned from this call is always completed, no need to attach
            // a listener.
            Task<GoogleSignInAccount> task = GoogleSignIn.getSignedInAccountFromIntent(data);
            handleSignInResult(task);
        }
    }

    private void handleSignInResult(Task<GoogleSignInAccount> completedTask) {
        try {
            GoogleSignInAccount account = completedTask.getResult(ApiException.class);

            // Signed in successfully, show authenticated UI.
            Intent intent = new Intent(MainActivity.this, HomePage.class);
            startActivity(intent);
        } catch (ApiException e) {
            // The ApiException status code indicates the detailed failure reason.
            // Please refer to the GoogleSignInStatusCodes class reference for more information.
            Log.w("Error", "signInResult:failed code=" + e.getStatusCode());
        }
    }

}
LogCat 
2020-04-03 23:17:04.513 9826-9857/com.willdong.highfidelitymockup I/FA: Tag Manager is not found and thus will not be used
2020-04-03 23:17:04.642 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:04.914 9826-9826/com.willdong.highfidelitymockup W/Error: signInResult:failed code=12500
2020-04-03 23:17:04.917 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:05.070 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:05.076 9826-9857/com.willdong.highfidelitymockup D/FA: Connected to remote service
2020-04-03 23:17:05.687 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:05.756 9826-9826/com.willdong.highfidelitymockup W/ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@2cad1b4
2020-04-03 23:17:05.891 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:06.103 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:06.195 9826-9826/com.willdong.highfidelitymockup W/Error: signInResult:failed code=12500
2020-04-03 23:17:06.318 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:06.456 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:06.964 9826-9826/com.willdong.highfidelitymockup W/ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@8f6bd57
2020-04-03 23:17:07.294 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:07.414 9826-9826/com.willdong.highfidelitymockup W/Error: signInResult:failed code=12500
2020-04-03 23:17:08.234 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:18.596 9826-9857/com.willdong.highfidelitymockup D/FA: Connected to remote service
2020-04-03 23:17:18.776 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:20.431 9826-9857/com.willdong.highfidelitymockup D/FA: Application going to the background
2020-04-03 23:17:20.656 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:31.462 9826-9857/com.willdong.highfidelitymockup D/FA: Connected to remote service
2020-04-03 23:17:32.167 9826-9826/com.willdong.highfidelitymockup W/ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@3bc556e
2020-04-03 23:17:32.497 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:32.592 9826-9826/com.willdong.highfidelitymockup W/Error: signInResult:failed code=12500
2020-04-03 23:17:32.813 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:32.955 9826-9826/com.willdong.highfidelitymockup W/ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@587f8e8
2020-04-03 23:17:33.233 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:33.377 9826-9826/com.willdong.highfidelitymockup W/Error: signInResult:failed code=12500
2020-04-03 23:17:33.691 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:43.187 9826-9857/com.willdong.highfidelitymockup D/FA: Connected to remote service
2020-04-03 23:17:43.353 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
2020-04-03 23:17:44.935 9826-9857/com.willdong.highfidelitymockup D/FA: Application going to the background
2020-04-03 23:17:45.138 9826-9869/com.willdong.highfidelitymockup E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.\
Ошибка 
V/FA: Activity paused, time: 522954395
V/FA: Connection attempt already in progress
D/FA: Connected to remote service
V/FA: Processing queued up service tasks: 2
E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
D/FA: Application going to the background
E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: INVALID_SENDER. Won't retry the operation.
V/FA: Inactivity, disconnecting from the service

Некоторые вещи, которые я уже пробовал

  1. Добавление поддержки по электронной почте через console.developers. goolge

  2. Добавление ссылок поддержки для ссылки на домашнюю страницу и ссылки на политику конфиденциальности (хотя я не был уверен, что именно поместить в эти места ... я просто поместил то же, что было в " Авторизованные домены ")

Добро пожаловать на сайт PullRequest, где вы можете задавать вопросы и получать ответы от других членов сообщества.

Похожие темы

...