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.
Related
I have built a app in android studio and would now like to publish it however I am very confused with the process for this. From Android studio I have generated a signed APK file which can be seen in the image below.
I see however that Google play console wants the files in the .AAB file type. How do I generate this/ what is it. The upload console can be seen below.
This is my first app upload so my questions may make no sense, please let me know in the comments below if there is anything I need to change or additional information required.
Any additional help with publishing apps on google play store will be greatly appreciated.
.AAB refers to "Android App Bundle", select Android App Bundle instead of APK after you clicked Generated Signed Bundle / APK, the rest of the procedure is more or less the same. You may refer to the official documentation for more information
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.
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 know this question was already ask 100, 1000-times, but still I have a problem with it and I already tried a lot by signing the application and to visualize the map after putting them in the store.
What I actually want is the following: Putting the android application in the store under "Alpha" version. This works without a problem, the application works, the only thing that doesn't work is the google map, its a white screen, I think the problem is that there is something wrong with the signed api key, but I don't know what.
Firstly I did the keystore with this dialog.
Afterwards I generate the SHA1 value for the google map api key with this new keystore. Putting the SHA1 value into the console.developers.google.com link under credentials to generate a PUBLIC API ACCESS key under the following format: XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX;PPP.PPPPP and then I generate a key and copied this in the manifest file.
And finally I either generated a signed apk for the store or directly signed it by building it for the smartphone.
But still it doesn't work. I don't know what the problem could be... Maybe one of you can help me.
OK guys thanks for your help I found the error... Don't know how it came to this error but still I found it.
As you may know android studio will generate you an google_maps_api.xml file. When I opened the file there was the key written "ALZ...." but when I check in the multi languages place, there was written "YOUR_KEY_HERE", so something went wrong... After putting the key in the multi language place it worked :)
I had a similar problem (since the key generation was device specific). I don't know whether its the best answer or not but following solved my problem:In Google Developer Console(after creating project and enabling apis), I generated a browser key without entering any ip and used that as my key.That solved my issue.
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.