I have created Android client id for expense.loremipsum.tracker for my app. Actually I have created 2 id, one for by Eclipse keystore and one is for my signed key store. My application is live so I can not change package.
I have tried by deleting project and recreating project but couldn't work. Now I am not able to create client id for expense.loremipsum.tracker.
I refereed this question. Should I contact Google? Now from any project I am getting this error This client ID is globally unique and is already in use
My application is live and not working Google Plus client.
Edit
Right now I have not any Android client id regarding this expense.loremipsum.tracker and I am still not able to create single one for this.
Try going here to see if you have old projects:
https://cloud.google.com/console#/project
What ended up resolving this for me is what Ketan suggested. You need to go here:
https://code.google.com/apis/console/
Then click the drop down menu in the top left underneath your name (if you don't have any, create a basic project, then go to the dropdown menu). From there, you can see in Ketan's screenshot that there is an undelete. Undelete your project.
Once undeleted, go to the 'API Access' section. If you have anything under 'Client ID for installed applications', click delete of this on the right. Then you can delete this project again.
Once that was done, I was able to recreate my game services OAuth 2.0 in the Google Play Game Services page at the regular Google Play publish page:
https://play.google.com/apps/publish/
No need to contact Google.
If you delete project it doesn't mean you delete client id.
You have to delete client id because it's unique.
If you have deleted project then Go to undelete>(your project) and delete client id
Go to the https://console.developers.google.com/project
select a deleted project then in the sidebar on the left, expand APIs & auth. Select credentials and click delete button to deactivate the clientID.
Related
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.
I finally got a useful response from Google support through email, providing just a clue on how to start the recovery process:
I understand you're receiving a Client ID error when trying to link your app to a Game Services project. This error message is displayed because your package ID and SHA1 are already in use by another Client ID.
To resolve this issue, please use the steps below to delete the Client ID from your Google Developers Console (formerly Cloud Console).
Important: Do not delete the Google Developers Console project before deleting the Client ID. If you’ve already deleted the project, you will need to undelete it from your Projects list.
1. Use the following URL to access the project - https://console.developers.google.com/project/186639667931
2. Select APIs & auth > Credentials
3. Under “Client ID for Android application” click the “Delete” button.
4. Try linking your app in the Play Console again. If you’re unable to view or undelete the project linked in step 1, please try accessing it while logged in with the primary email address on your Play developer account.
There was no 'Client ID for Android application', but there was an 'OAuth Client' under 'OAuth 2.0 client IDs', so I deleted that. That still had an old SHA1 number as it wouldn't take my current one. So I wasn't really deleting something with my current number, but deleting this deleted the whole client and brought up a blank screen. Here there was a bit of a trap. I added my current SHA1 number to that screen, which it accepted. Now I was able to get a response from the Google Play site again from my app, although its response always was 'Cannot access services'.
As it turns out, this screen was the default screen, which is 'Google Play Android Developer'. I'll have to research what this is for sometime, but what I needed to add a SHA1 to was my actual app name. I ultimately found buried in the dropdown list at the very top, next to 'Google APIs', among example apps I had downloaded and 'Google Play Android Developer'. I still couldn't add my current SHA1 to it until I went back and deleted the 'OAuth Client' from 'Google Play Android Developer'. This bought the same default screen back, so I went back to the dropdown, selected my app name, and then was able to finally add my current SHA1 back to it.
So deleting a SHA1 appears not to be a permanent exile from Play Services, just the start of a tricky process to get it reestablished.
I want to get the GCM Browser Key in the Developer Console, but the latest Developer Console doesn'tshow the Browser Key selection.
If I click Credentials, it doesn't show anything apart from one single key. I don't know what is the procedure to get the Browser key.
If anyone knows let solve my problem. Thanks in Advance.
You need to go to Google Developer Console and follow this steps:
Create Project
Enable Library
Create Credential (*)
(*) when u create credential, click on Restrict Key and add your specific Key restriction.
Update: There is now a visible note in the GCM docs saying:
Starting from Sept. 2016 new server key can only be created in the Firebase Console using the Cloud Messaging tab of the Settings panel. Existing projects that need to create a new server key can be imported in the Firebase console without affecting their existing configuration.
Update: It seems that using the Server Keys from the Firebase Console is the sure thing solution.
If you are just starting to use GCM, instead of creating a project in the Google Developers Console, do it in the Firebase Console. After creating the project, simply use the auto-generated Server Key. Here are the steps where to find the Server Key:
Go to your Firebase Console and click on CREATE NEW PROJECT.
Fill in your desired Project Name and select your Country. After this, the new Project should be active.
Then on left-side panel, click on the gear button and select Project Settings.
Then go to the Cloud-Messaging Tab.
For old GCM projects, you can simply Import the project to the Firebase Console:
Go to your Firebase Console and click on IMPORT PROJECT.
Select the project you want to import and your country.
Click on ADD FIREBASE. After this, the new Project should be active.
Then on left-side panel, click on the gear button and select Project Settings.
Then go to the Cloud-Messaging Tab.
Basing from the image, you've already generated an API Key. But gonna include the steps for visibility:
Go to your Google Developers Console
On the left-pane, click on Credentials
Under the Credentials Tab, Click on Create Credentials
Select API Key
With that, the API Key is already available. However, it will default as a No Restriction key. You may click on Restrict Key to add the restriction corresponding to what you need the API Key for.
I'm not entirely sure, but for a Browser Key, I think you would need to set the HTTP referrers (web sites) restriction. Since basing from the other restrictions:
IP addresses (web servers, cron jobs, etc.) = Server Key
Android apps = Android Key
iOS apps = iOS Key
You may try the API Key generated without any restrictions, however, it is highly encouraged for you to add the corresponding restriction as a security measure against unauthorized usage and quota theft.
I am getting exception as below:
Well, I've used or say copied same code as this shown in google doc https://developers.google.com/google-apps/calendar/quickstart/android .And I know it is the same error which is already mentioned in troubleshooting part of this doc but as mentioned in its solution, I had checked my SHA1 fingerprint and also package name and all the stuffs but still getting same error. And also I tried to google and followed each and every link the google suggested but nothing works for me so my last option was STACKOVERFLOW and so I am here. Please help if any one can. Thanks in advance.
Also I forgot to mention, it says "Unregistered Android application" it means that the OAuth2 client ID I created is not found by the app but I don't know how can I make it find my OAuth2 client ID and solve my problem.
Please make sure that:-
You enabled calendar API in google console for that project you are using, as the link provide in your response.
Also match your package name in AndroidManifest is similar to the package you mentioned in google dev console with SHA.
Try to create an Oauth client id under corresponding project in google console. Follow the steps in this link.
To create an OAuth 2.0 client ID in the console:
Go to the Cloud Platform Console.
From the projects list, select a project or create a new one.
If the API Manager page isn't already open, open the console menu and select API Manager.
On the left, click Credentials.
Click New Credentials, then select OAuth client ID.
Note: If you're unsure whether OAuth 2.0 is appropriate for your project, select Help me choose and follow the instructions to pick
the right credentials.
Select the appropriate application type for your project and enter any additional information required. Application types are described
in more detail in the following sections.
If this is your first time creating a client ID, you can also configure your consent screen by clicking Consent Screen. (The
following
procedure
explains how to set up the Consent screen.) You won't be prompted to
configure the consent screen after you do it the first time.
Click Create client ID.
Based also from this related post, you have to give permission from your calendar configuration (Calendar configuration -> Share this calendar) to the email account specified into Google Api Console (email adress).
Hope this helps!
Started to add Firebase to my app. For that, I had to add SHA1 configuration but got this error
An OAuth2 client already exists for this package name and SHA-1 in another project. You can omit the SHA-1 for now and read more about this situation and how to resolve it
So I followed up this linke as proposed and got to the instructions that seemed to be relevant to my case (i.e., starting to add Firebase to an existing app):
If you just created this project or aren't very far into adding Firebase to your app, the simplest approach is to delete your project and instead import your existing Google project.
But, when I went ahead to delete my Firebase project, I got this scary message:
This is a permanent action. All apps contained within this project will also be deleted.
My app is in production! I cannot delete it! Is this message written just from a Firebase console perspective? Can I be sure my existing app (originally defined in a regular Android project) will NOT be deleted?
After some investigation on my own realized the Firebase project can safely be deleted without loosing access to my original app. Here are the details.
What's deleted is the corresponding GCP project (i.e., with same project ID); assuming you created a new project (which is what I did) - you'll get an automatically generated new GCP project and it will be deleted when you delete the new Firebase project.
The GCP original GCP project which corresponds to my app (already on Google Play) is not touched.
In case of a mistake, it's always possible to restore the original GCP project (see here). I didn't need that but it was easier to decide to verify the above 2 bullets knowing this option exists.
I have been struggling with setting up my app in the Android Developer Console. Specifically, I need to set up and assign a client ID to the App (or linked app, not sure), however, I am unable to do so.
Any attempt to create the client ID I am told one already exists. Yet, I can not publish my app since the app is not linked to one with a client ID.. or so I gather.
//I am unable to press the create button. I am blocked out from doing so.
///the step required to publish.
You need to provide the correct package name that your app uses as well as generate the fingerprint using key gen and paste that key there. Without those, you cannot create a client id for your app. The required steps are explained in great detail in their help pages.