Android gives 'ERROR: DEVELOPER_ERROR' when signing in

[jimmirbn]

When signing in using
await GoogleSignin.signIn();
It opens the dialog, I sign in but gives the 'ERROR: DEVELOPER_ERROR'

Steps to Reproduce

• Install react-native-google-signin and follow the setup guide for Android
• Import react-native-google-signin and make a function that calls await GoogleSignin.signIn()
• Sign in with your google account
• When the dialog closes the error occurs

Expected Behavior

• Opens dialog
• Signs in
• Returns userInfo, id and accesstoken

Actual Behavior

• Throws an error saying 'ERROR: DEVELOPER_ERROR'

Environment

• react-native: 0.60.4
• react-native-google-signin: 2.0.0
• play-services-auth: 15.0.1
• SDK version: 25
• Build gradle: 3.4.2
• Tried two newest versions of android, Q & Pie

[Uemerson]

I have the same error ...

[longnk-1447]

. the same

[jaaphou]

the same

[shekharskamble]

same here

[atrimn]

anyone ? started happening to me

[shyamalVixplor]

Hi! Is there any solution?

[AdeilsonSuperlogica]

Same here too...

[mauricioalexandres]

Same here... :(

[ccorneliusHsv]

Same

UPDATE: I was able to get it working by adding the debug key to the Firebase project. Was able to retrieve the debug SH1 key via keytool -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore -storepass android -keypass android

[AdeilsonSuperlogica]

I solved this problem following this steps https://stackoverflow.com/questions/47437678/why-do-i-get-com-google-android-gms-common-api-apiexception-10

[Chbe]

I solved this problem following this steps https://stackoverflow.com/questions/47437678/why-do-i-get-com-google-android-gms-common-api-apiexception-10

Did you both add new credentials to API Console and add your key to your Firebase project? I'm getting "duplicate fingerprint" if I do both.. If i skip adding cred to API console I'm getting error message: "Must specity an idToken och an accessToken". I'm using GoogleSignIn.configure()

This is my code:

        await GoogleSignin.configure();

        const data = await GoogleSignin.signIn();

        // create a new firebase credential with the token
        const credential = firebase.auth.GoogleAuthProvider.credential(data.idToken, data.accessToken)
        // login with credential
        const firebaseUserCredential = await firebase.auth().signInWithCredential(credential);

[AdeilsonSuperlogica]

I solved this problem following this steps https://stackoverflow.com/questions/47437678/why-do-i-get-com-google-android-gms-common-api-apiexception-10

Did you both add new credentials to API Console and add your key to your Firebase project? I'm getting "duplicate fingerprint" if I do both.. If i skip adding cred to API console I'm getting error message: "Must specity an idToken och an accessToken". I'm using GoogleSignIn.configure()

This is my code:

        await GoogleSignin.configure();

        const data = await GoogleSignin.signIn();

        // create a new firebase credential with the token
        const credential = firebase.auth.GoogleAuthProvider.credential(data.idToken, data.accessToken)
        // login with credential
        const firebaseUserCredential = await firebase.auth().signInWithCredential(credential);

Yeap, I added the debug key sha1 in my project, but the accessToken not return in the signIn method like the doc https://github.com/react-native-community/react-native-google-signin#3-userinfo, you need get the token with method getTokens https://github.com/react-native-community/react-native-google-signin#gettokens.

Sorry my bad english... :D

[reidkersey]

I wanted to add my 2 cents. I thought I had everything setup correctly, then I realized I had a file called debug.keystore in my android/app folder.

I used the command keytool -list -v -keystore C:\Users\reidk\Documents\Git\Pr ojectR\android\app\debug.keystore -alias androiddebugkey -storepass android -keypass android to read the sha1 key from the react-native debug keystore. Then I added that to firebase, and now everything works great!

[brayanL]

Is necessary to generate the Keystore file through command line, I had the same issue with a published app, I generated the Keystore with Android Studio, so I contacted with Google support and they help me and I generate new Keystore file with the following tutorial: https://facebook.github.io/react-native/docs/signed-apk-android, they update the keystore of my published app and after three days the DEVELOPER ERROR is gone.

[aashishgaikwad]

I was also facing the same issue. My debug keystore's SHA1 was not working. I solved it by adding following code in android/app/build.gradle

signingConfigs {

• debug {

•    storeFile file(MYAPP_RELEASE_STORE_FILE)
  

•    storePassword MYAPP_RELEASE_STORE_PASSWORD
  

•    keyAlias MYAPP_RELEASE_KEY_ALIAS
  

•    keyPassword MYAPP_RELEASE_KEY_PASSWORD
  

• }
  release {
  ...
  }
  }
  Also added my release key SHA1 to firebase console.
  Source: https://github.com/react-native-community/react-native-google-signin/blob/HEAD/docs/android-guide.md
  FAQ / Troubleshooting section.

[vonovak]

hello, please see this doc improvement, it should help. https://github.com/react-native-community/react-native-google-signin/pull/737/files

if this does not help, please provide careful repro steps. Thanks.

[akashmohan]

for poor souls like me who used the android client id,

you have to add your web client id. not android client Id.

its quite obvious people might think they have to add the android client id since they are building it for android.
but it is the web client id that you have to add.

[sugaith]

@akashmohan got it.. just get the Web client (auto created by Google Service) ID from google console -> credentials

[amitbravo]

@reidkersey thank you very much, I was trying keytool -exportcert -keystore ~/.android/debug.keystore -list -v which ofcourse was giving me a SHA1 key but it was not working , after your comment I also look closer into my project/android/app folder and found that there is a debug.keystore key too (whose default password is "android" , incase some need to know ) so I tried keytool -exportcert -keystore app/debug.keystore -list -v running the command under my android folder and the key I got ,worked really well. thank. you.

[sanjanadhikaridev]

Hi there.
I have same issure.
Please help me.
componentDidMount() {
GoogleSignin.configure({
webClientId: "504314064456-ps5ib5d6b2f1ieqcnqplav327eea610s.apps.googleusercontent.com"
});
}
state = {}
signIn = async () => {
try {
await GoogleSignin.hasPlayServices();
const userInfo = await GoogleSignin.signIn();
this.setState({ userInfo });
} catch (error) {
console.log(error);
if (error.code === statusCodes.SIGN_IN_CANCELLED) {
// user cancelled the login flow
} else if (error.code === statusCodes.IN_PROGRESS) {
// operation (f.e. sign in) is in progress already
} else if (error.code === statusCodes.PLAY_SERVICES_NOT_AVAILABLE) {
// play services not available or outdated
} else {
// some other error happened
}
}
};
render() {
return (

<View style={{ paddingLeft: wp('5%'), paddingRight: wp('5%') }}>
Highlight

high-light
/ˈhaɪlaɪt/
<Text style={{ paddingTop: wp('5%'), paddingBottom: wp('5%'), paddingLeft: wp('15%'), fontSize: hp('2.3%') }}>noun
1. A mobile communciations assistant that reduces popup notifications to help you focus.
<Text style={{ paddingTop: wp('5%'), paddingBottom: wp('5%'), paddingLeft: wp('15%'), fontSize: hp('2.3%') }}>2. Your new best friend
<GoogleSigninButton
style={{ width: 192, height: 48 }}
size={GoogleSigninButton.Size.Wide}
color={GoogleSigninButton.Color.Dark}
onPress={this.signIn}
// disabled={this.state.isSigninInProgress}
/>



);

[mitesh-db]

I fixed it by entering correct SHA-1 in firebase console. Problem was I was using following command for generating SHA-1 from my project directory

keytool -exportcert -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore

Here path for the debug.keystore is in ~/.android folder which is different, my keystore was inside /android/app, So I followed this new path in command, which was in my project directory

keytool -exportcert -list -v -alias androiddebugkey -keystore ./android/app/debug.keystore

Then (1) copied the SHA-1, and (2) enter it in project of firebase console then (3) download the config file again and replace it in android/app folder then (4) remove the build and install again, it worked!

---

EDIT: For some reasons, on a few computer devices you also have to perform these steps.
-> Close the terminal and uninstall the application from the mobile device. remove android/build folder and remove android/app/build folder. Now install again on your device.

If you get error like ... Only one command is allowed: both -exportcert and -list were specified.
Solution: remove -exportcert from command, thus command will be ...keytool -list -v -alias androiddebugkey -keystore ./android/app/debug.keystore

[gbmahili]

I fixed it by entering correct SHA-1 in firebase console. Problem was I was using following command for generating SHA-1 from my project directory

keytool -exportcert -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore

Here path for the debug.keystore is in ~/.android folder which is different, my keystore was inside /android/app, So I followed changed the path in command

keytool -exportcert -list -v -alias androiddebugkey -keystore ./android/app/debug.keystore

Then (1) copied the SHA-1, and (2) enter it in project of firebase console then (3) download the config file again and replace it in android/app folder then (4) remove the build and install again, it worked!

I followed @mitjnextt steps and mine is now working. The only thing that I didn't do was to download the config file again, it still worked...not sure if that will bite me somewhere else but thanks a lot for the tip.

[julitroalves]

for poor souls like me who used the android client id,

you have to add your web client id. not android client Id.

its quite obvious people might think they have to add the android client id since they are building it for android.
but it is the web client id that you have to add.

I spend an week try solve this problem with my android app, thanks a lot! <3

[QuintonC]

We are having issues with this still.

We are using the web client id, not the android client id.

In development Google Sign In works. In release, Google Sign In does not work. Is there anything else that it could be?

Edit: Both of our SHA-1 keys (from debug keystore and upload keystore) are in our firebase console.

[julitroalves]

Google Sign In does not work

If you uploaded your app to Google Play you will need to add the SHA-1 key from GooglePlay to your firebase console too?

Go to your https://play.google.com/console/developers then select your app then go to Sign Certificate App.
Copy the SHA1-key and paste into Firebase console of your project, download the google-service.json file and put it on android/app folder build your app and test again in production.

[AndresTIY]

@julitroalves In my Google Play Console, Under Setup -> App Signing, I see 2 different key certificates.

1: App Signing Key Certificate
2: Upload Key Certificate

My Upload Key cert matches what I have in my Firebase console. Yet the App Signing Key Cert doesn't match anything I have in FB. Could this be a potential issue as to why Google Sign In isn't working in Production?

[MatheusPires99]

I fixed it by entering correct SHA-1 in firebase console. Problem was I was using following command for generating SHA-1 from my project directory

keytool -exportcert -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore

Here path for the debug.keystore is in ~/.android folder which is different, my keystore was inside /android/app, So I followed changed the path in command

keytool -exportcert -list -v -alias androiddebugkey -keystore ./android/app/debug.keystore

Then (1) copied the SHA-1, and (2) enter it in project of firebase console then (3) download the config file again and replace it in android/app folder then (4) remove the build and install again, it worked!

When a I run this command keytool -exportcert -list -v -alias androiddebugkey -keystore ./android/app/debug.keystore it ask me a "password for the key storage area".

[gamingumar]

I am getting this error in play store and not in debug mode. I have also copied SHA to firebase console :(

[mitesh-db]

Hey @gamingumar, Make sure you add SHA which is generated by the keystore you have used to upload the apk.
Also make sure your app bundle name on firebase is same as you are using it in your project.

[gamingumar]

@mitjnextt I resolved this issue, it was caused by wrong SHA. The reason was the confusion between firebase and google cloud project. They were 2 different projects in google cloud. I found out that firebase creates google cloud project by default.

[nizar-banna]

I am getting this error in play store and not in debug mode. I have also copied SHA to firebase console :(

+1

[goodhyun]

sometimes unprepared app/build.gradle could be the culprit.

signingConfigs {
        release {
            storeFile file("android-.jks")
            storePassword pass
            keyAlias "~~~"
            keyPassword pass
        }
        debug {
            storeFile file("android-.jks")
            storePassword pass
            keyAlias "~~~"
            keyPassword pass
        }
        // debug {
        //     storeFile file('debug.keystore')
        //     storePassword 'android'
        //     keyAlias 'androiddebugkey'
        //     keyPassword 'android'
        // }
    }

[martsaarmets]

I'm using Firebase. The solution for me was to copy the google-services.json file also under the subfolders for different variants. So I have this file in app/google-services.json and additionally app/src/dev/google-services.json, app/src/test/google-services.json, app/src/production/google-services.json etc. At first I thought that it's enough to have the file in the app folder like stated here but looks like this will not work by default.

Also, be sure which key is being used to sign your dev/test app and add your debug key SHA1 to the Firebase console. Use the signingReport task in Android Studio -> Gradle menu to double-check. Or unzip your .apk and check the cert fingerprint in the META-INF directory.

[sorold]

@SanjanaTailor did you find any solution?

I fixed it by making sure the sha1 key in my firebase android project is the correct one. I did that performing the following:

• Inside of my project folder, I cd into android and run ./gradlew signingReport'
• Copy the sha1 key under > Task :app:signingReport with the property and value **Config: debug**, and **Variant: debugUnitTest**
• Paste it in your firebase android project by clicking on add finger print

Make sure you have copied the google-services.json file inside of your /android/app/ folder

I'm not using firebase and this worked for me! This SHA1 is different from the ones generated by the keytool with the debug.keystore files on user/.android and and myapp/android/app, neither of them were working. I just created a new credential on the same app in the google console, didn't even need to delete the credentials from the old debug.keystore. Thanks!

[CyrusZei]

PRO TIP:

Even if you think you have the correct webClientId just copy it from firebase and paste it in.
Spent way to much time on debugging this

[ninjz]

For anyone banging their heads on this in the future. I had this issue in production after deploying my app to the Play Store. The problem happens because i'm using the managed app signing service so the Play Console actually manages the App Signing Keys and therefore your app would actually have a different signing key when deployed on the Play store..

To find that key you must go to the Play Developer Console under Setup > App Integrity > App Signing and find the SHA-1 certificate and enter that into your Firebase console.

[mdarifulislamroni521]

I solved it
at fast create webClientId from google cloud console web Application Credential . then create Android Credential with your package name and SHA-1 certificate fingerprint * . then configure like bellow =>

GoogleSignin.configure({
webClientId: 'your web client id here ',
offlineAccess: true,
});

i hope it will work for all . Thanks

[anujjoshi63]

For me, it wasn't working until I provided offlineAccess:true
GoogleSignin.configure({ webClientId: "...", offlineAccess: true });

[kranercc]

OFFICIAL SOLUTION IS THIS:
Use command:

 keytool -list -v -alias androiddebugkey -keystore android/app/debug.keystore -storepass android -keypass android

Copy the SHA1 from the output
Go to Firebase WEBSITE -> open project settings and look for where it says "fingerprint" or something about "Sha1" thats where you need to place it, if you cna't find that, create new project it will ask for it once you start a new project

[ducnv3]

Same

UPDATE: I was able to get it working by adding the debug key to the Firebase project. Was able to retrieve the debug SH1 key via keytool -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore -storepass android -keypass android

same my isssue, because SHA1 from here "keytool -list -v -alias aliasName -keystore app/keystore.jks -storepass passWordStore -keypass passWordKeyPass".
in this case, we need to generate SHA1 from above command from keystore file. this is production deploy for privateKey.
THanks u very much.

[kindacoder]

For anyone banging their heads on this in the future. I had this issue in production after deploying my app to the Play Store. The problem happens because i'm using the managed app signing service so the Play Console actually manages the App Signing Keys and therefore your app would actually have a different signing key when deployed on the Play store..

To find that key you must go to the Play Developer Console under Setup > App Integrity > App Signing and find the SHA-1 certificate and enter that into your Firebase console.

Yeah, the same issue I had. i was checking the release build and it was working fine but after pushing it to play store it was not working. But it's working now.
Thanks

[Oleksiiithouse]

One more step to try (that was my case of DEVELOPER_ERROR) is to check if you definitely typed correctly your package name that locates at <your_proj>\android\app\src\main\AndroidManifest.xml in google cloud field for android project. Make sure that typed package name starts exactly with 'com.' prefix. It is very stupid but while fighting with it I always typed my project name without this prefix so this throwed an error.

[danieldt232]

In my case It worked in development, but when I tried to use Firebase App Distribution it threw DEVELOPER_ERROR.

Turns out that Firebase re-sign test bundles with a new sha-1 that you can find here:

These steps worked for me:

1. copy the sha-1 from "View certificates" window in Firebase App Distribution
2. Add the copied sha-1 to "project settings" > SHA certificate fingerprints
3. Download again the "google-services.json" (that now includes the new fingerprints) and replace the old one in your code
4. Build and release again

[huy-lv]

I have tried all above suggestion but nothing work at all :(

[CyrusZei]

1. Remove the app from the google play store 2. Generate an new APK to upload to google play 3. Voila, you will have the new SHA-1 that is on your app in the google play store.

…

On Sat, 24 Dec 2022 at 15:50, Lê Vũ Huy ***@***.***> wrote: I have tried all above suggestion but nothing work at all :( — Reply to this email directly, view it on GitHub <#706 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGR3T3P3KST6SRLQXET7NDWO4ESFANCNFSM4IMFTPEA> . You are receiving this because you commented.Message ID: ***@***.*** com>

-- With regards Cyrus_Zei [ *Developer* + *Designer* = *Unicorn*]

[huy-lv]

Found my problem:
In my folder android/app there is a debug.keystore file, but I run keytool command to get SHA1 with ~/.android/debug.keystore file.
Rerun with correct keystore file and everything will be fine. Hope this help someone :D

[CyrusZei]

Yes, there are two SHA-1 keys and you can enter this command and you can see the SHA-1 key keytool -list -v -keystore ./android/app/debug.keystore -alias androiddebugkey -storepass android -keypass android

On Sun, 25 Dec 2022 at 06:12, Lê Vũ Huy ***@***.***> wrote: Found my problem: In my folder android/app there is a debug.keystore file, but I run keytool command to get SHA1 with ~/.android/debug.keystore file. Rerun with correct keystore file and everything will be fine. — Reply to this email directly, view it on GitHub <#706 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGR3T6VMLQASTGDQZG2NVTWO7JTLANCNFSM4IMFTPEA> . You are receiving this because you commented.Message ID: ***@***.*** com>

-- With regards Cyrus_Zei [ *Developer* + *Designer* = *Unicorn*]

[sergiycheck]

tricky steps for android

1. generate new debug.keystore

sudo keytool -genkey -v -keystore my-upload-key.keystore \
  -storepass android -alias androiddebugkey -keypass android  \
  -keyalg RSA -keysize 2048 -validity 100000
  -dname "CN=serhii, OU=debug, O=private, L=home, ST=0, C=UA"

3. place new debug.keystore instead the old ones in the ./android/app folder
4. generate new sign in report cd android && ./gradlew signingReport
5. paste sha1 keys into the firebase console android project settings input sha1 fingerprints
6. download google-service.json
7. copy the value of client_id with client_type: 3 to the webClientId property.
8. build the android app
   Steps described helped me and I was able to sign in with google after many hours of struggling.

[apalm]

I spent more time than I'd care to admit on this, so writing down what I found, in the hope that it'll be helpful to someone.

• I'm not using Firebase
• I'm using Expo, and I'm using managed credentials
• My GoogleSignin.configure call:

GoogleSignin.configure({
  webClientId: YOUR_WEB_CLIENT_ID,
  offlineAccess: true,
});

What I found:

• google-services.json isn't needed. Don't include googleServicesFile in app.json/app.config.js.
• In Google Cloud Console, create 3 OAuth 2.0 Client IDs:

1. Application type="Web application". Pass this client ID to GoogleSignin.configure as webClientId.
2. Application type="Android". Make sure Package name is correct. Get SHA-1 certificate fingerprint by running keytool -list -v -alias androiddebugkey -keystore android/app/debug.keystore -storepass android -keypass android from the project root.
3. Application type="Android". Make sure Package name is correct. Get SHA-1 certificate fingerprint by running eas credentials from the project root. Select Android as the platform, then select your build profile.

[ayodeji334]

In addition to this, I changed the third one to the SHA-1 certificate fingerprint from the production keystore.

[sergioisidoro]

+1 - After a long time I realised that it HAS to be the SHA1, not the SHA256

[marcomelilli]

@apalm thank you! This is the final solution or those who are not using firebase and are using EAS managed credentials

[vlastami]

I spent more time than I'd care to admit on this, so writing down what I found, in the hope that it'll be helpful to someone.

* I'm not using Firebase

* I'm using Expo, and I'm using [managed credentials](https://docs.expo.dev/app-signing/managed-credentials/)

* My `GoogleSignin.configure` call:

GoogleSignin.configure({
  webClientId: YOUR_WEB_CLIENT_ID,
  offlineAccess: true,
});

What I found:

* `google-services.json` isn't needed. Don't include `googleServicesFile` in `app.json`/`app.config.js`.

* In [Google Cloud Console](https://console.cloud.google.com/apis/credentials), create 3 `OAuth 2.0 Client IDs`:


1. Application type="Web application". Pass this client ID to `GoogleSignin.configure` as `webClientId`.

2. Application type="Android". Make sure `Package name` is correct. Get `SHA-1 certificate fingerprint` by running `keytool -list -v -alias androiddebugkey -keystore android/app/debug.keystore -storepass android -keypass android` from the project root.

3. Application type="Android". Make sure `Package name` is correct. Get `SHA-1 certificate fingerprint` by running `eas credentials` from the project root. Select `Android` as the platform, then select your build profile.

Also, people, don't forget to update the google-service.json (download the new one if you updated the SHA-1 in the Firebase). 😄

[realadamsmith]

I spent more time than I'd care to admit on this, so writing down what I found, in the hope that it'll be helpful to someone.

• I'm not using Firebase
• I'm using Expo, and I'm using managed credentials
• My GoogleSignin.configure call:

GoogleSignin.configure({
  webClientId: YOUR_WEB_CLIENT_ID,
  offlineAccess: true,
});

What I found:

• google-services.json isn't needed. Don't include googleServicesFile in app.json/app.config.js.
• In Google Cloud Console, create 3 OAuth 2.0 Client IDs:

1. Application type="Web application". Pass this client ID to GoogleSignin.configure as webClientId.
2. Application type="Android". Make sure Package name is correct. Get SHA-1 certificate fingerprint by running keytool -list -v -alias androiddebugkey -keystore android/app/debug.keystore -storepass android -keypass android from the project root.
3. Application type="Android". Make sure Package name is correct. Get SHA-1 certificate fingerprint by running eas credentials from the project root. Select Android as the platform, then select your build profile.

It doesnt make sense to me that Web application client ID worked for logging in from my Samsung Gakaxy Android phone. I got the idToken,
but serverAuthCode is still Null
{..."https://www.googleapis.com/auth/youtube.readonly"], "serverAuthCode": null, "user": .....}

[robinderozario]

For those using eas-build with a development client, in my case, eas inserts different signing credentials during the build process. In other words, it is not using the SHA1 specified in the google-services.json file. To make the google signing work in development, I had to add the SHA-1 Certificate Fingerprint listed in the Expo.dev console, under "Project Settings" > "Credentials" > "Android Keystore", to my Firebase project (which also adds it to Google Cloud API). I personally can't remember ever uploading credentials to Expo, but it could be the case. If they're autogenerated, I can imagine a lot more developers must face the same issue which is why I'm sharing this.

[NorseGaud]

Non-firebase users that let Google sign their app: Under the Google Cloud Console > APIs & Services > Credentials > Client ID for Android, set your SHA-1 to the App signing key certificate found in the Play Store Console > Setup > App signing.

You'll know it works because Verify app ownership under the Client ID for Android page will say "Your app ownership has been verified".

[naguibihab]

I spent more time than I'd care to admit on this, so writing down what I found, in the hope that it'll be helpful to someone.

• I'm not using Firebase
• I'm using Expo, and I'm using managed credentials
• My GoogleSignin.configure call:

GoogleSignin.configure({
  webClientId: YOUR_WEB_CLIENT_ID,
  offlineAccess: true,
});

What I found:

• google-services.json isn't needed. Don't include googleServicesFile in app.json/app.config.js.
• In Google Cloud Console, create 3 OAuth 2.0 Client IDs:

1. Application type="Web application". Pass this client ID to GoogleSignin.configure as webClientId.
2. Application type="Android". Make sure Package name is correct. Get SHA-1 certificate fingerprint by running keytool -list -v -alias androiddebugkey -keystore android/app/debug.keystore -storepass android -keypass android from the project root.
3. Application type="Android". Make sure Package name is correct. Get SHA-1 certificate fingerprint by running eas credentials from the project root. Select Android as the platform, then select your build profile.

I am using an Expo managed project, so i don't have direct access to the android keystore in the same way that i would in a bare react native project (in other words I can't run keytool -list -v -alias androiddebugkey -keystore android/app/debug.keystore -storepass android -keypass android because I don't have an android folder) Is there another way I can get the SHA-1 certificate fingerprint @apalm ?