Google-signin: Android - React 0.21.0 - INTERNAL_ERROR

[m0ngr31]

Getting this error on Android. This shows when I click a button that runs GoogleSignin.signIn(). It doesn't make it to the login view at all, just errors out. I have my debug token set as the fingerprint, not sure what else to check?

Error: INTERNAL_ERROR
    at GoogleSigninError.Error (native)
    at new GoogleSigninError (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:93823:188)
    at http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:93875:8
    at EventEmitter.emit (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:50043:23)
    at MessageQueue.__callFunction (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:48673:23)
    at http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:48577:8
    at guard (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:48531:1)
    at MessageQueue.callFunctionReturnFlushedQueue (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:48576:1)
    at DedicatedWorkerGlobalScope.onmessage (http://localhost:8081/debuggerWorker.js:39:56)

[devfd]

can you try with latest NPM version please ?

also make sure the json config file is accessible. The sample app is running fine if you want to have a look.

[m0ngr31]

Same error on the newest version (0.4.3) after a clean build. Also, I incorrectly put RN as version 0.20.0 in the title, I'm running on 0.21.0.

And my config file is where it should be.

[m0ngr31]

I just tried the example app:

WRONG SIGNIN Error: INTERNAL_ERROR
    at GoogleSigninError.Error (native)
    at new GoogleSigninError (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:46246:188)
    at http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:46298:8
    at EventEmitter.emit (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:9114:23)
    at MessageQueue.__callFunction (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:7872:23)
    at http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:7776:8
    at guard (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:7730:1)
    at MessageQueue.callFunctionReturnFlushedQueue (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:7775:1)
    at DedicatedWorkerGlobalScope.onmessage (http://localhost:8081/debuggerWorker.js:39:56)

[devfd]

did you install google apps on your simulator ?

[webschik]

@devfd , hi!

I've also got an error WRONG SIGNIN Error: INTERNAL_ERROR on Genymotion simulator and
Error: A non-recoverable sign in failure occurred on my Nexus 5.

[devfd]

you get this error when you run the sample app ?

[webschik]

@devfd, no, it's mine. I'm using RN 0.20. So, I'm going to try your sample and come back with feedback.

[webschik]

@devfd, I've tried your example on RN 0.21.0 and have the next results:

1) Genymotion - WRONG SIGNIN Error: INTERNAL_ERROR
2) Nexus 5

WRONG SIGNIN Error: unknown status code: 12501
    at GoogleSigninError.Error (native)
    at new GoogleSigninError (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:15923:188)
    at http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:15975:8
    at EventEmitter.emit (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:18551:23)
    at MessageQueue.__callFunction (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:17181:23)
    at http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:17085:8
    at guard (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:17039:1)
    at MessageQueue.callFunctionReturnFlushedQueue (http://localhost:8081/index.android.bundle?

[m0ngr31]

@devfd Couldn't get Goople apps on my emulator, but was finally able to get an android device to test on and the error didn't occur, so I think it's working as intended.

[Hari70a]

@m0ngr31 and @devfd

I have the same issue which you had faced previously

WRONG SIGNIN Error: unknown status code: 12501
    at GoogleSigninError.Error (native)
    at new GoogleSigninError (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:15923:188)
    at http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:15975:8
    at EventEmitter.emit (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:18551:23)
    at MessageQueue.__callFunction (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:17181:23)
    at http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:17085:8
    at guard (http://localhost:8081/index.android.bundle?platform=android&dev=true&hot=false:17039:1)
    at MessageQueue.callFunctionReturnFlushedQueue (http://localhost:8081/index.android.bundle?

Have you fixed the issue?
I have tested the app in emulator and device.(Note: I have google apps installed in both device and emulator)

Nothing worked for me.
Please suggest the solution if it worked fine .

[m0ngr31]

@Hari70a I only had problems when it was trying to login without Google Services installed.

[Hari70a]

OK @m0ngr31

BUT I have google apps installed in both device and emulator(genymotion)

I have also tested the example project in the plugin. Still I have the same issue.
But suggest me some idea to fix it.

Thanks in advance

[prithsharma]

I am facing the same issue, but only when I include a webClientId and offlineAccess field in the configuration.
It was all working fine with an empty object in the configuration. Since my server needs to make some calls on the backend, I included webClientId and offlineAccess in the configuration. And it started giving the following error:-
A non-recoverable sign in failure occurred
Any ideas? @devfd ?

[prithsharma]

I think the issue here is about the signing configuration of the app and whether it matches with the SHA1 used to generate the google configuration files. Note that the if you might be having different keystores for debug and release, so make sure the google-services.json file you are using was generated using the SHA1 of the right keystore file.