The request failed because the android package name and fingerprint are already in use

The fingerprint you specified is already used by an Android OAuth2 client ID in this project or another project

I noticed my SHA1 number showing from the gradle view signing report in android studio was different from the one I had originally. I thought maybe it was from changing computers a year ago. My game app was still able to access leaderboards and achievements. I when to my Google API dashboard I noticed the ‘OAuth client’ had my old SHA1. It wouldn’t let me change it to my new SHA1, saying it ‘had already been used by this client or another client’, although I had no other clients. The mysterious ‘Anroid client 1’ and ‘Android client 2’ had neither the old or new SHA1. Underneath the ‘OAuth client’ was ‘OAuth client (auto created by google service)’ which had my new SHA1. I went ahead and deleted that one, despite a warning it gave me that it had been used 147 times in the last week (evidence of impending senility on my part I suppose). It seemed I had to delete it to free up the number for my ‘OAuth client’ that was not auto created.

Now it appears I’m screwed, as it still gives me ‘the already in use message’ when I try to change the SHA1, and my game app can no longer access Google Play Services at all. I’m thinking I should have deleted the ‘OAuth client’ instead. Can I recover from this? Will it free up over time? Another post suggested 7 days for clients to be removed, although I don’t see a button to delete the whole client, and am concerned over the deletion of the API codes on the same page.

EDIT 3/30 — It looks like I may have lost this number permanently, although (I’m hoping) it only affects my Leaderboards and Achievements, not Firebase, Inapp Purchasing, or Ads. I can roll my own Leaderboards and Achievements in Firebase anyway. New projects with different package names give me the same unusable SHA1 in the Gradle signingReport.

Источник

SOLVED The request failed because the android package name and fingerprint are already in use Create OAuth client ID

SOLVED The request failed because the android package name and fingerprint are already in use Create OAuth client ID

SOLVED The request failed because the android package name and fingerprint are already in use:

Many users are facing this issue when they try to «Create OAuth client ID» below is the solution to fix the error

Step 1: create a new empty folder on your desktop

Step 2: Copy and paste your Keystore file into the new empty folder

Step 3: from the new folder open the command prompt using «cmd» like the below image example

Step 4: in command prompt use the following command line: keytool -keystore yourkeystore.jks -list -v

Do not forget to replace the Keystore name before using the command line: keytool -keystore THIIS-NAME-SHOULD-BE-YOUR-KEYSTORE-NAME-ENDING WITH. KEYSTORE OR.JKS -list -v.

Step 5: Now you will see SHA-1 certificate fingerprint, copy and paste that’s it.

Do not forget to refer and subscribe if the above steps solved your issue, if not please comment so that we can help you.

Easy SEO Check — SEO Check Easy

By Me A Coffee

Best Cheapest Hosting! Easy SEO Check

GET STARTED

Order Premium Web Hosting get a free .COM domain Free. Free SSL and Cloudflare [Limited Time Offer] — Buy Now! CLICK HERE

Источник

The request failed because the Android package name and fingerprint are already in use

I’m creating Consent Screen for my app as I’m using some sensitive permission while providing Google Sign-in, so now from September 2021 onwards it’s compulsory to provide a consent screen for which one needs to get their permissions/scopes verified by google.

For submitting a verification request there must be an OAuth Client ID associated with the request.

So, when I’m trying to create a new OAuth Client ID, it says «The request failed because the Android package name and fingerprint are already in use», but there’s no OAuth Client ID in my list.

I was having one API key with the same package name and SHA-1 and I deleted it, but the error is still the same.

Please help as I’m unable to figure out what’s the issue?

See also questions close to this topic

In my android app, I have two roles (doctor and patient). Both have their own fragments and their own activities. Both of them are able to post comments. Where I am using Samsung j5 6 to run the app. I do not understand why my current activity is destroyed and goes back to patient activity even from doctors activity when I try to add a comment by clicking on post button.

I have three TextViews (Rating, VotesRating and Votes) in one line but only one of them can be visible at the same time. That’s why I added a Barrier with ids of those TextViews movie_rating,movie_votes,movie_rating_votes . And then I use that Barrier to add another TextView below it (with description of a movie). But as you can see in the screenshot the description text can be above that Barrier . This is such a buggy library.

For most ViewHolders it works ok, this is crazy

Is it possible to have a spinning icon (like progressbar) as the material button icon?

I would like to set the state parameter in my Redirect URI as described in https://developers.google.com/identity/protocols/oauth2/web-server#redirecting

How can I set the state in my redirect URI?

But Google tells me:

RFC 8628 doesn’t state that the client_secret parameter is needed for Device Access Token Request: https://datatracker.ietf.org/doc/html/rfc8628#section-3.4

When I do such a request using Google API

I get the following error:

If I pass client_secret , it works.

I’d be grateful if anyone could answer my two questions:

1. Why does Google API require client_secret for the device flow? OAuth 2.0 for TV and Limited-Input Device Applications doesn’t offer any explanation.
2. Is it safe to expose client_secret , assuming that my client belongs to the «Client ID for TV and Limited Input» type? I assume it’s generally discouraged, so I’d like to limit this question to Google API only. My application can be downloaded, and the secret is basically hardcoded, thus exposed to everyone. If the secret gets leaked, I’m wondering what are the implications.

I made google sign-in button with react-native, and it worked at first, but now it doesn’t.

I figured out that useAuthRequest doesn’t return idToken anymore, so I searched for solutions and I found useIdTokenAuthRequest , passing responseType: ‘id_token’ to useAuthRequest , but their problem was that they are returning idToken only while I need both idToken and accessToken .

How do I get both accessToken and idToken?

Hello People of Google Cloud ! A new Developer on Google Cloud based in Morocco, From the begining of my using of Google Cloud Console for our IT Project. I faced a huge problem related to User Interface experinece from the first time ! The majors of web pages on Google Cloud Console not showing and working well, but other users like me here in Morocco, they haven’t any problem with user interface. As you see in this picture below: enter image description here For this I want why ? and How can I resolve it?

Anyone help me on this, espeically the GoogleCloud Team support Please !

I’ve been able to ssh into the server before, but now for some reason I can’t. I’m suddenly getting «: Permission denied (publickey)» when trying to ssh into the server. Even when trying to ssh from the google cloud console it just stays on «Connecting» «Could not connect, retrying(2/3). «

But now, when I try to create an OAuth client Id I can´t because the following message :

«The brand that you’re trying to edit has been deleted. Recreate your brand.»

I have tried to recreated brand, filling form of «Consent screeen» but I can´t. It is showing the error : «An error occurred while saving your app»

In developer console of chrome I read the message returned and I got this :

Now, the project it is in an inconsistent status and I can´t continue.

Any help would be aprreciated in order to reset the consent screen o create a new one

Источник

Restricting usage for an Android key for a Google API

My question is about how to properly set the package name and SHA-1 certificate fingerprint in the Google Developers Console in order to restrict usage of my Android API key to my app.

When I don’t have anything set in the «Restrict usage to your Android apps» section, my requests to the Google Translate API work properly. The API responds normally with status code 200 and my expected result.

But when I specify a package name and SHA-1 certificate fingerprint for my app using the Developers Console, I consistently get 403 Forbidden responses like the following:

The request looks like the following. Notice that there’s no referer header in the request:

I’m assuming that the error message indicates a package name or SHA-1 fingerprint problem, despite its message about a «per-IP or per-Referer restriction». While browser keys allow the setting of a per-referer restriction, I’m using an Android key with nowhere to set a per-IP or per-Referer restriction.

I’m sure I have entered the package name correctly in the Google Developers Console. I’m reading the package name from the package attribute on the manifest tag in my Android manifest file.

I’m also sure I have the SHA-1 fingerprint set correctly in the Google Developers Console. I’m reading this value from my keystore using the command keytool -list -v -keystore /path/to/my/keystore . I get the same value when I read it from the APK file using keytool -list -printcert -jarfile myAppName.apk . I’m installing that same APK file using adb.

Here’s what I see in the Developers Console:

I’ve tested this on multiple devices running stock Android. I get the error response on wifi and on the cell network, whether I’m proxying the traffic or not.

When I remove the restriction from the Developers Console, the app works properly again.

What am I doing wrong here?

Note: Several similar questions have been asked before, but with no adequate answers. I don’t want to use a browser key or remove the restriction altogether. I want to get the usage restriction to work properly.

Источник

Google sign-in Android with Firebase — statusCode DEVELOPER_ERROR

I try to implement Google login in my Firebase connected Android app. When I run the app and press Google Sign In button — nothing happen. And I receive this error in onActivityResult: Status .

My code looks like this:

I’ve added JSON config file in app/ directory and added dependencies:

I am looking for solution hours already. Please help!!

13 Answers 13

DEVELOPER_ERROR means Google Play services was unable to find a matching client from the console based on your SHA1 and package name. You can add SHA1s in the settings page on the Firebase console for a given package name, or add a new package name through the Add Firebase to your Android app button.

In general, some things to check for:

• Make sure your package name is what you expect — e.g. its the one in your build.gradle, and its not being overriden in a build variant or product flavor.
• Make sure you have registered your debug and release SHA1 keys in the console.

If Google Play App Signing is enabled for your app, then it will replace your release signing key with the one on Google’s server before publishing.

You can check if it is enabled from: Google Play Console -> Release Management -> App Signing .

In my case, to resolve the error I had to:

1. copy the SHA1 from the ‘App signing certificate’ section
2. add it to the Firebase projects general settings section
3. regenerate the json file
4. add it to the project
5. re-upload the apk

Error code 10 is constant value of CommonStatusCodes.DEVELOPER_ERROR which implies you have misconfigured your project

What you can do

check if SHA from PlayStore Console and Firebase Console are same.

Читайте также:  Шнур аукс для андроида

Copy SHA from Google Play console

paste it into Firebase Console

What else you can do?

Display meaningful messages in plain English case of failure

I had the same problem. What happens is this you have a SHA1 debug and release SHA1. Normally we used only SHA1 Debug and generate the .apk signed to google play, but when we use google sigin you must enter the firebase release of SHA1.

To view the release SHA1 use the following command:

Then enter this SHA1 on the Firebase

This answer SHA1:

Hope I helped you.

Had the same issue. But worked fine after I cleaned and rebuilt the project. 😀

I created new debug SHA1 key using following steps and replaced SHA1 key in my project settings. it worked for me.
-Open Your Project.
-Click on File menu -> New -> Click on Google -> Select Google Maps Activity -> Click on Finish. -Android studio would generate automatic google_maps_api.xml file.
-You can get debug SHA1 key in this file.

Replace this SHA1 key in project settings, Then download new google-services.json from settings and replace it in your project as your certificate_hash and client_id will change.

I had the same issue and I got it working by doing these steps:

1. Add DEBUG_KEYSTORE SHA1 fingerprint to the firebase project. use the following command(MAC/LINUX)

2. Now Generate a signed apk of your project. The process includes generating a keystore for your app’s release version. Copy the path of the newly generated .jks file.

3. Now generate RELEASE_KEYSTORE SHA1 fingerprint using the following command

4. Copy the new SHA1 from the output and add it as another SHA1 fingerprint in your firebase application console.

Now you are good to go! —- Hope! it helps.

I think you need to change your play-service version.

See Firebase Android Codelab to add Firebase Auth dependency to your app/build.gradle file.

Try to update your play-service in gradle as below:

The application is misconfigured. This error is not recoverable and will be treated as fatal. The developer should look at the logs after this to determine more actionable information.

While creating the OAuth key, you need to make sure you are giving correct package name. This means the package name that comes in your manifest file.

If you are using multiple modules (e.g. some library like FirebaseUI-Android), then make sure while creating the key, you use the package name from which you request Google authentication.

I had the same issue. After 2 days of pain, I observed that my release SHA1 was incorect (I used to get it using the keytool in java/bin and it gave me a bad SHA1. Probably because now Android Studio uses its own java package and not the JDK). Better way to get the corect SHA1 here SHA-1 fingerprint of keystore certificate

Click Here (Google Developer guide line) and create new project for Firebase console this link is set with default setting, so you don’t need to add it manually

If your app is on release mode/production, then you have to get the SHA1 from your-release-store.keystore. If your app is on development mode, then you have to get the SHA1 from your-debug-key.keystore. Copy all the SHA1 to your Firebase project settings > add fingerprint.

This is how to get the SHA1 from your keystore file:

After spending two hours on this. Trying out everything mentioned here and on this github issue. I still got the same developer error.

What worked for me is to force android studio to use a new debug signing key and add the new key to firebase console.

When you generate the signingReport in android studio it also print where your keystore is located. Something like:

I renamed the debug.keystore to debug.keystore_ and the lock file also. Then I did a clean and rebuild in android studio. It automatically created a new keystore. Use the signingReport again and add the new key to the firebase console project.

This solved the issue for me.

Note: To double check the package name of the debug apk. Use the aapt2 tool: https://developer.android.com/studio/command-line/aapt2

By default, it was located in the android-sdk\build-tools\ \aapt2.exe path for me.

Источник