Use of Credential Manager API

[brenie2]

Hello,

We received an inbox in Google Play Console, stating that we were utilising legacy Google Sign-in APIs, which are deprecated and planned to be removed in 2025.

In our React Native mobile app, we were previously using the “@react-native-google-signin” external library, as recommended in "react-native-firebase" documentation. However, to migrate to Credential Manager with this external library, we have to sponsor, which is not what we want.

Therefore we changed the mechanism used in our app. We now use following mechanism to let users sign in with Google:

import firebaseAuth from '@react-native-firebase/auth'
const provider = new firebaseAuth.OAuthProvider('google.com')
await firebaseAuth().signInWithRedirect(provider)

How can we know if this uses legacy Google Sign-in APIs or the new Credential Manager API? This information can’t be found in "react-native-firebase" documentation nor on Google.

Note: we use v19.2.2 of the “@react-native-firebase/auth” package.

If this uses legacy Google Sign-in APIs, how can we migrate to the new Credential Manager API without sponsoring to “@react-native-google-signin”?

Thanks in advance for your help.

[mikehardy]

How can we know if this uses legacy Google Sign-in APIs or the new Credential Manager API? This information can’t be found in "react-native-firebase" documentation nor on Google.

I don't know, you're first here and likely will have to investigate. You'll need to find the symbols associated with legacy APIs and search for them

Note: we use v19.2.2 of the “@react-native-firebase/auth” package.

Asking for support + help on non-current versions is inefficient in my experience. You run the risk of wasting your time with false-positives indicating problems that may be there in v19 but already fixed in current.

However, to migrate to Credential Manager with this external library, we have to sponsor, which is not what we want.

Sometimes "free" software has costs associated with making sure everyone can buy groceries it seems! You may find with a quick economic analysis that sponsoring is less expensive than whatever time you'll spend yourself...

[brenie2]

Ok, thanks for your reply!

I don't know, you're first here and likely will have to investigate. You'll need to find the symbols associated with legacy APIs and search for them.

Let me know if your investigation leads to something.

Asking for support + help on non-current versions is inefficient in my experience. You run the risk of wasting your time with false-positives indicating problems that may be there in v19 but already fixed in current.

We'll indeed update this library to the latest version, to be sure that support is optimal.

[mikehardy]

Let me know if your investigation leads to something.

To be clear: I'm not planning on investigating, this isn't a use case of mine and I don't believe these are APIs that are within the react-native-firebase module. It appears they are in react-native-google-signin unless shown otherwise if you investigate