I am making an android application that needs Google sign in API integration,
After configuring the Project I got credentials.json however all over internet people are referring to google-service.json. I am getting status code 10. I want to know whether google-service.json is credentials.json or I am making a mistake here.
No, they are not the same.
The google-services.json file is necessary for Google sign-in. Look at this question (particularly the second answer) to help you get signed in.
Related
I got an email from Google that says:
We have detected a publicly accessible Google API key associated with the following Google Cloud Platform project
and they point at the api key inside my google-services.json file and at a url of someone hosting my apk.
The google-services.json file is just what I got when following the Firebase instructions and put it where it said to put it. So did I do something wrong?
No you are not supposed to edit it, you have to restrict it.
Note that if you are using Android Studio, you can get the signing report see this accepted answer here.
Error Message: Your site 'website.com' has not been linked through the Digital Assets Link protocol to your app. Please link your site through the Digital Assets Link protocol to your app.
Hi
Dealing with this issues since past week. Did a lot of google and engaged play store support team also without any resolution. Therefore, posting it here hoping somebody would have already faced this issue too.
For instant app upload to play store I have already uploaded the assets json file to the specified path and I am able to get that file via simple GET request. So, there is no access control required over the asset json file.
In android studio also digital asset linking results in success as shown below:
But whenever I try to publish it to playstore it always gets stuck at below:
Any help would be highly appriciated. Thanks.
ok I figure out the exact problem. It is the issue with SHA256. I provide SHA256 of my release key. However i need to provide the SHA provided by play console. Go appsigning section and copy SHA256 of your aap and replace it with your release SHA256.
You may refer with this thread which encounters the same issue. Try to follow the steps provided in the documentation and also see the discussion in the SO post. It stated that if your app is enrolled into Google Play Signing, APKs should be signed with upload key, while assetlink.json should have release key fingerprint.
I have tried so many times to access https://developers.google.com/mobile/add
but I can't.
when I access the site, I just see circle progress thing, and it never disappears.
Is there a problem in google or my account has the problem?
Thank you.
My app is already in Play Store using older version of Google analytics and I have the similar problem with the endless spinning circle when I try to update my app and download the file google-services.json....
I double check my analytic property and the Google Play Console etc, try it on different platforms, browsers...
And then I realize that the document said "Google Developer Console".
I login in https://console.developers.google.com
and create a project for my app after I done that I am able to get the google-services.json from
https://developers.google.com/mobile/add
I am doing some modification in an existing apk that i got from my client to modify. I have decompiled application using apktool, changed some resources (like some strings from strings.xml) and recompiled/built it again using same tool. Then I signed using one_click_signer tool that I found somewhere of the google.
But when I install it on my device then google maps does not work anymore as it was working with original apk on the same device.
I have searched a lot about this but did not got any solution.
I reviewed this link and many more and come to conclusion that I need to sign the apk with same key that was in original apk.
So can anyone please tell me:
how can I sign the apk again with the same key and make map work?
or is there any other way to make maps work properly?
Solution That I found and worked for me:
Thanx for
#apmartin1991's answer . .
I created a google api console project and got got the generated key.
then I replaced that key in android-manifest.xml file and resigned the application.
It worked.
You will need to contact your client to get the .keystore file so you can sign it with the same key OR you can sign it with your own key and allow your key to be used with google maps, You can do this from the Google API console.
However if your clients app is on the appstore and you want to update that you MUST use the same key or it will be impossible to update it.
You need .keystore file to use the same key. If you dont have .keystore file you need to generate a new one and register a new key in google maps console.
You have all the official instructions here.
This question already has answers here:
How to build an APK file in Eclipse?
(12 answers)
Closed 2 years ago.
I finished my android app now and i want to upload to the android market.. I have already bought the android license to upload i just want now to know what i need to do with my app.. I heard you need something signed and you need some key.. I can't remember all i heard but is there some complete guide for this or something i can read when i want to make my application into .apk and upload to market.. Im intrested in full guide so i might learn in the future how it works..
I did search the web before for this but they were so unclear guides how to do it.. Didn't help me much at all..
The Android publishing guide explains this step by step. You must sign your app with your private key and generate the signed .apk file, as explained in the linked guide.
The easiest way is to use Eclipse to sign your application. During the signing process you will be prompted to create a password. Make sure you write this down as you will need this to sign updates to your app. Once you've signed your APK, sign into the Android market (http://market.android.com/publish) and upload your binary.
Here's information on signing
http://developer.android.com/guide/publishing/app-signing.html#releasemode
Also, DO NOT lose the keystore file you need to create when signing your app. Without the original keystore file you will not be able to update your app to a newer version, because you won't be able to upload a newer version if it was not signed with the same certificate.