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.
Related
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 adding Google Maps into my application for the first time.
I have gone through several tutorials for getting the Google Maps API key for deployment.
But every where the first step indicated is to create a debug.KeyStore OR the create our own application keyStore
Then copy our SHA1 and paste it with the package name while generating API Key.
My small doubt is:
I am giving an Update of my application and added Google Maps in my version 2.
I do have the keyStore of my application that is already live on the play store.
So what do i do now as I already have my key and have to use the same key for the Update.
I dont want to mess up things at the time of deployment.
Please Help.
You must be use that keystore file which is already within the application on Google Play Store. Because if you create new keystore file then you have to regenerate process again.
So you have to go to with your old one keystore file.
You should be using the keystore that you already have. Basically you have no other option.
I have to sign my APK and Google market provide me a key which is something like
YOUR LICENSE KEY FOR THIS APPLICATION Base64-encoded RSA public key to
include in your binary. Please remove any spaces.
MIIBIjANBgasdfasdfdaskqhkiG9w0BAQEadfadfasdFAAOCAQ8AMIIBCgKCAQEAuacIf........
How can I sign my APK with this key and how include this key in my binary?
I had the same question. Finally found that the RSA public key on Dev-Console is for "licensing". It means that the app can use the key to query if the user has a current and valid license for using your app or the services in it.
This is totally different from signing an apk.
http://developer.android.com/google/play/licensing/index.html
I too am like the original poster asked wondering what to do with the lisence key generated by the developer console on my way to publishing in the Google Play store.
While all the above posts show how to export and create keystore etc in Eclipse or from a command line, none of them answer what the dadgum key Google offers up is for. Do I need to add it somehow? I see no way to specify the key Google generated as a "licening key" in the Google Play Developer Console, and NOTHING tells me HOW to bind THAT key to my app.
I already know how to export a signed app using eclipse but that does not have the Google Play key. If someone can point me in the right direction it is much appreciated.
OK I have figured it out. The licence key is irrelevant to signing your app and is for licensing purposes within your app.
The Android Developer site has a great walkthrough for signing apps here.
Seeing as though you have your key, you just need to create a password-protected keystore file ".keystore" by using the keytool shown here. This will prompt you to enter all the details that Android requires for a signed app.
You can check other answers here and here.
Eclipse makes it really easy to export by right clicking on your project and selecting "Android Tools > Export Signed Application Package".
Good luck!
we are trying to use google play's apk expansion file since our package is too big. After following the instruction in http://developer.android.com/guide/google/play/expansion-files.html and follow some posts in stackoverflow. we managed to have our code running.
But unfortunately, we are keep getting STATE_FAILED_FETCHING_URL. is there anything wrong? should we set anything before we start?
we have already put the apk and expansion file through the developer console.
any suggestion? thanks a lot.
[UPDATE]
I found the reason is because I haven't added the google account to test account, and not working with the apk signed with the same keystore as I uploaded to publish account. But after I succeeded once, it is ok to work with the apk signed by default debug keystore in eclipse. Besides, I forgot to click the Activate link to make my draft become active.
I hope that I can be clear; I know there are a lot of threads on the Google Map API, but I have exhausted my brain trying to fix my problem with the maps. Please tell me what I have wrong here.
I understand there are two Google Map API keys.
1) API key, for a market published app. Maps will appear once the app is published.
2) Debug API key, only works on emulator or side loaded to the phone for testing.
My partner and I are working on an app together from different PC’s. We each have our own debug api key.
1) He sends his app folder from his .android folder
2) I drop the files into folder in my .android folder
3) I import the project into eclipse
4) Replace his API key with mine.
5) Run application
He gets maps displaying on his application, but I do not. I get the gray grid.
Do I need to build a new APK of the app before the maps will appear? Does this new APK have to be created exactly like he did his?
Does the path to my APK need to be in the same folder as my keytool.debug?
How does the fingerprint relate to the APK?
Please clarify, we are stumped.
The maps API key is linked to the keystore which was used to register. You will need the debug.keystore that was used to register for the API key. Here are some quick instructions I found on how to do this.
Sharing one keystore is much easier than changing the reference to a new maps API key every time you make a revision. I'm not sure why your method isn't working though.