I was using Google MAPS API and Oauth2. I wanted to move them to new gmail and firebase project. I deleted old account's firebase and google cloud api projects.
Firebase has been moved successfully with same SHA-1 KEY. But even though I changed package name fully, Google says "fingerprint is already used" and I can't move my sha1 for new gmail's oauth2.
How can I fix this? (I checked almost all posts about this but there is no obvious solution)
Related
I am trying to use firebase otp authentication for my web application but haven't found any docs related to same on firebase website. Is it possible to do so if yes then how to. Please guide me.
I have searched online for documentations but only found those related with an android app. I am building a website which requires registration and sign in. This registration is to be validated by authenticating users phone number for which I am required to use firebase authentication.
I have an app on Play Store. I am using Firebase Cloud Messaging for sending Notifications to users. Yesterday, I got email from Google that my key is exposed and I need to fix it or my app will be removed from Play Store by 11 January. Please explain how can I fix this in simple language.
Log into your firebase console and create a new server key by pressing add server key and replacing it with the old one.
I am getting the following error when attempting to connect to Google Play Services:
-- E/Volley﹕ [131] BasicNetwork.performRequest: Unexpected response code 403 for https://www.googleapis.com/games/v1/players/me?language=en_US
-- E/SignInIntentService﹕ Access Not Configured. Google Play Game Services API has not been used in project 608941808256 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/games/overview?project=608941808256 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.
com.google.android.gms.games.server.error.GamesException
I have configured my application on Google Play Developer Console and it's ready for testing. I have linked an app to it and enabled appropriate APIs in the Developer Console (Google+ Api, Google Play Services Api, Goole Play Android Developer Api ..).
I used the SHA1 keys that the apk uses, which I added to the OAuth 2.0 list in the Developer Console.
I am using sample code provided by Google, have added my app_id in the ids.xml file (1058015326796), which does not match the project ID in the error message.
How do I connect to Google Play Services properly? Have I forgot some step in setting up the access? Why is the project ID in the error message different from the ID I am using in the application?
608941808256 is a telling project ID - it means that for some reason Google Play services didn't map your app to your client ID. This look up is generally performed by SHA1 and package name.
You mention you added your SHA1 to the developer console, which is good - maybe then check that the package name is correct. For example, maybe you append ".dev" to the package name for development builds or similar, or the package name in your build.gradle is different than the one in the Developer Console.
Remember to look under OAuth 2.0 client IDs as well - that's the section that needs to have matching values.
I spend 4 days with the same problem.
I had created project in Google Play Developer Console with all needed API's
Like you I used the SHA1 keys that the apk uses, which I added to the OAuth 2.0 list in the Developer Console.
And the solution in my case was :
to generate signed APK.
I was sending GET request for Account Data with app that was just build and run.
After 4 days of trying i read
Before you can publish an app that retrieves an OAuth 2.0 token for Google REST APIs, you must register your Android app with the Google Cloud Console by providing your app's package name and the SHA1 fingerprint of the keystore with which you sign your release APK.
and thought I will generate signed APK, and it worked.
Ps. I doesn't use Volley so i don't know if this will help you.
I got the same error.
[Problem 1] Wrong app_id, achievement/leaderboard IDs in the ids.xml!
[Solution 1] Replace or set the ids from google play game console.
[Problem 2] Use debug key and release key by mistake
[Solution 2] Be careful using the key(SHA1), pay attention whether it is debug or release.
I am using Google Apps API for my application with OAuth2. ,but I get an error.
Error: invalid_client
no support email
Request Details
That’s all we know.
If you create OAuth credentials BEFORE you set the support email address in the consent screen, then it appears that you will always get this error, even after setting the support email.
I resolved this by setting the support email, and then recreating all necessary OAuth ids in the credentials page.
In the Google Developer console make sure that you have added a product name and an email address under. Apps & auths -> consent screen.
Update: This shouldn't be to much of a problem anymore. Google made a change in the console that wont let you save anything until you have updated these items.
In Google Developer Console turn Gmail API on.
GDC > Dashboard > Use Google APIs > Google Apps APIs > Gmail API
Be sure that you are set up the setDeveloperKey with your EMAIL ADDRESS offred in Google Console whe you create a Client ID for web application.
Had the same problem and the solution was:
Set my email
Recreate the keys
Activate Google API+ from API Library
1) Fill out the info email address and produce name as well as other details in the 'consent' screen on google's console when you generate the keys.
2) And make sure when you copy paste the ClientID and ClientSecret code from google to your workspace (IDE), there might be some unwanted spaces inbetween
Check with the google console and remove it.
Hope this helps,
--happy coding!
Their is no bug with regard to the maps. I already signed the apk with release keystore ,
the API Keys are registered in my account
It perfectly works in any devices.
What's the problem is when it is uploaded with the client account in google play store
and downloaded in their device, the map displays white.
Question:
1.Does it affect the application if the API keys are registered to my account and the one who upload the app is not my account ?
Answer:
The API key is associated with the apk package and it's keystore and not a user account.
First you need to create a keystore for you app. Refer to http://developer.android.com/tools/publishing/app-signing.html
Next go to https://console.developers.google.com/project and create a project (if don't have one already).
On your project page go to API's & auth > APIs enable Google Maps Android API v2
Next go to API's & auth > Credentials and create a new Key for Android applications. Follow those instructions careful and you it will generate you an API to use on your manifest. (Remember to use the keystore you used to sign your app for play store and not your debug keystore)
More info:
https://developers.google.com/console/help/new/#generatingdevkeys
Good luck
I also face this problem . you need to
signed your application with the system from which you generate SHA-1
fingerprint for Google Api
.
Check Your API Key whether it is the same with the one in Console and in your Manifest.