I have a keystroke from google for my app. When I try to Export signed application package from eclipse, it gives me an option to either create a new keystore or to use an existing one.
As per my understanding I must use the "Base64-encoded RSA public key" that I got from Google. But there is no way I can download the key directly from the page where google displays it for me.
Can someone please let me know if I have to import it in someway or am I missing something?
Or should I just copy paste the key to some (binary) file in my project? Please help!
I have a keystroke from google for my app.
But there is no way I can download the key directly from the page where google displays it for me.
Which page is that? You shouldn't download a key in order to sign your application.
Or do you mean the debug.keystore which comes with the installation of the Android bundle? You can use it during development, but you need to create your own key when releasing the App. (Google Play won't accept an apk signed with the debug keystore)
If you are not releasing yet and you want to use the debug keytore - search your system for 'debug.keystore'. On Windows it can be in:
C:\Users\USERNAME\.android\debug.keystore
The passwords for the keystore and the android alias are android.
If however you want to create a new key for yourself - you can do that using the provided keytool as described here.
Finally, if you need an additional key for accessing some Google API (eg. Maps) with your App, then from the online developer console you need to create an additional Android key with the same fingerprint, as the one that you are signing the App with. This additional key is typically included in your manifest after that.
For reference, you can create new keys for your App here: https://console.developers.google.com
Related
due to a disk failure I have lost the signing key of my app.
But I know exactly the alias and password I used.
Two things :
- Can I create a new file with the exact same info and use it to sign my app again?
- If not if there a tool to get the file from the apk (I know the password and alias, no need to crack it)
Many thanks
Can I create a new file with the exact same info and use it to sign my app again?
If not if there a tool to get the file from the apk (I know the password and alias, no need to crack it)
No and no, sorry. You will have to create a new key and deploy the app to Google Play as a new app. Then, make sure you have multiple backups of your signing key.
I have an built an application 6 months ago that uses google maps v1. Now I want to publish it in the Google Play Store
When I was working on it I did the procedure required to obtain a key. As far I remember I used the cmd to generate a MD5 that I pasted in a site.
I have saved the file with the result which is something like that
letersandnumbers
This key is good for all apps signed with your certificate whose fingerprint is:
hex:hex:hex:hex:hex:hex:hex:hex:hex:hex:hex:hex:hex
Here is an example xml layout to get you started on your way to mapping glory:
<com.google.android.maps.MapView
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:apiKey="letersandnumbers"
/>
When I compile and run the application on my phone that is on debug mode, it works.
When I try to use the letersandnumbers as a key to sign my application the result is different. The application shows only grid and not the map.
The way I sign my application is the following:
1)File->export->android application
2) I select the project and use the lettersandnumber key mentioned
above.
3) I put the file on the SD card of the device and install it.
Am I doing something wrong?
Please help! Switching to maps v2 is not an option
UPDATE:
I managed to follow the guide Daniel writes about in the comment. However when I use the new key in the manifest and sign the app with this new Key it does not work...
I am trying to use maps version 1.
You will not have any success using maps API v1. It is deprecated since december and you can't get new keys since march. Rework your app to use API v2.
Sounds like you need to generate the hash key for your signed cert. From what you explained it seems like you have added the hash for your debug key cert only which is why when your debugging the maps work. So once again, you need to run the keytool command.
keytool -list -v -keystore mystore.keystore
This time make sure you refer to the keystore your using to sign your app when you export it. Then enter the new hash into the google API console -> API ACCESS -> Create new Android Key. You'll be given a new API key that you will need to add to your maps entry in the layout.xml file you referenced above.
I saved my project.apk file, and I was reading this document: http://developer.android.com/guide/publishing/app-signing.html#setup and they kind of skip over the details of how to actually obtain a release key.
Is there a site that just generates this key for me? Does Goolge app store have to know about the key too? I am confused :)
Thanks,
Alex
Scroll down to "Signing in Release Mode"
You can create a self-singed certificate, or use a signing authority. I expect most people use a self-signed cert.
DO NOT LOSE that cert or you will not be able to make updates to your app.
And the easies way for signing is using Eclipse and ADT.
You just right click on your project folder and select:
Android Tools>Export Signed Application Package
Sorry if this a stupid question but really want to know what is the purpose of registering the hashkey on facebokk app page. I nowhere use it in my application(if we have to use it then please let me know where).
The question is How my app will be authenticated using hashkey??
And how to sign my app using hash key???
Thanks for your Help!!!
Facebook requires an additional layer of security for mobile apps in the form of an
application signature. You need to put your Android application signature into your
Facebook application settings. You can generate a signature by running the keytool that
comes with the Android SDK. The following shows how to export the key for your app using
the debug defaults specified by the Android SDK and Eclipse.
Also Check this Hash Key for Single Sign-On
Also if i put another Key Hash which is not generated by me
You will get Invalid key Error if you use Wrong Key Hash .
Check this Login failed for Invalid Key
It's used as another layer of security. On how much it's actually used, I'm not 100% sure. But, here's a few links that might help.
Use of the Facebook App Key Hash
https://developers.facebook.com/docs/mobile/android/build/#sig
I'm publishing an Android app at Amazon AppStore and doubted about integration with Facebook.
The instructions on Facebook's site are very clear in case if I'm using just my certificate to sign app. However, as I understand Amazon signs the app with its own certificate and, therefore, I should generate a new Key Hash for Facebook SDK.
So my question is: how do I generate Key Hash for Amazon Appstore signed app (if I don't have their keystore)?
We got in touch with Amazon through their Developer Portal (Help -> Contact Us -> Questions about application signature) regarding this issue.
Looks like they enabled a flag for our app that gives us an option to sign the binary ourselves. When uploading a binary, you get an option: Amazon will sign the binary or I will sign the binary.
If you want to sign the binary, the process looks like this:
Step 1: You upload an unsigned APK
Step 2: You download the processed binary that contains their injected code
Step 3: You sign the processed binary with your key and upload again
This way, you can reuse your existing Key Hash for Facebook SDK.
Amazon provides you the hash. Under the "Binary File" tab, there is a section titled "Appstore Certificate Hashes". You just need to copy the sha1 base 64 hash to the Facebook app settings.
I solved it like this:
I run the amazon app on my kindle fire without having the key.
When the invalid parameter error was displayed I wrote the key down and entered in in my facebook app description page.
The key was something like '-aQe9Ti2YD9.....' and but it did not work.
Then I replaced the '-' by '+' and voila, it worked.
Please make sure to replace '-' and '_' by '+' and '/' in the key string that is displayed by the facebook app! ( See http://de.wikipedia.org/wiki/Base64 section URL applications )
AFIK, they double sign the apk with their key, your signature is not removed. You might want to have a look at an apk downloaded from Amazon to confirm. Since your signature/certificate is still there, presumably it should work without you having to do anything different than for the Android Market. I haven't tried it though (can't download from Amazon).
I got in touch with them through the contact us on the bottom and asked for the key hash for facebook connect.
They replied with the hash less than 5 min. after I sent them the questions.
Done!