conflict with another applicaton using react native google signin

[walty8]

I have two react native applications and both use react native google signin, today I found that the login session of the two applications will actually interfere with each other.

Steps to Reproduce

1. open application A, do GoogleSignin.signIn() with Google account A.

2. open application B, do GoogleSignin.signin() with Google account B

3. kill application A, and start application A with GoogleSignin.signInSilently(). Token of Google account B will be collected.

Expected Behavior

Application A should get the token of Google Account A

Actual Behavior

Application A got the token of Google account B

Environment

iOS 15.5

Remarks

I suspect it's because the Google login session is shared among different applications. And signInSilently will actually log into the latest logged in account?

I could somehow save the refresh and access tokens into the local storage, but I have no idea how to feed the tokens back to the instance of GoogleSignin.

Thanks

[muhabutt]

I am also facing the same issue, a duplicate project in android. version 8.0.0.

[mnebuerquo]

@muhabutt That seems to be a separate issue from this one. Two instances of this module causing manifest merge errors, right?

[vonovak]

Hello and thanks for reporting,
@walty8 this sounds like a fairly serious bug, but at the same time I find it highly unlikely. Could you report this at the native google sign in SDK repository? https://github.com/google/GoogleSignIn-iOS

This package is only a wrapper on top of it so the problem likely originates there.

Thank you 🙂