I'm following this tutorial to create a Turn Based Multiplayer game: https://developers.google.com/games/services/console/enabling
Under the Specify client ID settings section, they say to run:
keytool -list -keystore [path-to-debug-keystore]
That's fine because they also mention the location of the debug keystore: "On Windows, the debug keystore can be found at C:\Users[USERNAME].android\debug.keystore."
They also say to run this command:
keytool -list -keystore [path-to-production-keystore]
But they don't mention where the release/production keystore is.
...where is it?
You generate the production key yourself. Read Sign Your App in the android developer documentation.
Related
I was working with google map. In debug mode, it was fantastic. For release mode I tried to get the release SHA1 key from my windows10 hp probook. But i got some encrypted text instead of SHA1.
My command is as follows:
C:\Program Files\Java\jdk1.8.0_45\bin>keytool -exportcert -alias razon** -keystore E:\keystore\keystore.jks
The output was as follows along with some unknown signs that are unable to write here:
0S10 U8810dhaka10Udhaka10U
410608143654Z0S10 U8810dhaka10Udhaka10U
Then I created another API key for google map from Developer console with a SHA1, used previously in another project. With this API, the map is working in release mode but only in my device(Nexus 5, os6.1).
My Questions
How can I get the actual SHA1?
What can I do now? Please help.
You can use the keytool -list -v command (documentation):
keytool -list -v -alias razon** -keystore E:\keystore\keystore.jks
More easiest way:
Double click on the signingReport. You will see your debug and release SHA1 fingerprint. But before that you must have to set the keystore file from Project structure.
In order to do that, go to File>Project Structures...>app>Sigining>+
After that give a name and locate the store file(keystore or .jks) and provide your alias and password.
Then Click OK.
Then again go to File>Project Structures...>app>Build Types and there you will see debug and release. Select each of them and change the Sigining Config value to you newly created one.
I am trying to implement AppInvites. I have gone through all steps written here https://firebase.google.com/docs/invites/android
And constantly get RESULT_CODE = 3, what have I done wrong?
Just to be sure it's not your code, you can download Firebase's quickstart samples from here: https://github.com/firebase/quickstart-android. Make sure to update the app-level gradle file with the right package name.
The guide you followed is a little incomplete, and doesn't explicitly mention the need to provide your app's SHA1 key when setting up your project in the Firebase console. Here's how to add the SHA1 key for a release certificate and a debug certificate to an existing Firebase project:
How to find the SHA1 for your keystore:
In command prompt, navigate to your Java installation. You'll be using Java's built-in keystore utility.
For the release certificate, type the following:
keytool -exportcert -list -v -alias <your-key-name> -keystore <path-to-production-keystore>
Note the SHA1 key it provides.
For the debug certificate, type the following:
keytool -exportcert -list -v -alias androiddebugkey -keystore %USERPROFILE%\.android\debug.keystore
Again, note the SHA1 key it provides. Since this key is unique to each Android development environment, feel free to repeat this step for each environment you want to build from.
Once your have your SHA1 keys, enter them both into your Firebase project:
Go to your Firebase console.
Click on the three overflow dots on the project in question and click "Manage".
Click SHA1 and enter your first key.
Click SHA1 again and enter your second key.
From there, you just need to download the new google-services.json file and add it to your project's /app directory.
When you sign and distribute your Xamarin Android apps the wizard helps you create keystore for your app. However, wherever I looked on my mac I could not find the actual .keystore file anywhere. So how am I supposed to get the SHA-1 fingerprint for that keystore?
SHA1 fingerprints are stored within the same keystore files.
Visual studio has an unique feature to open such files.
Just double click the file after creating it inside Xamarin. It will give you the SHA1 Fingerprint.
For windows users,
Go to this path or where ever you have your keytool.exe file
C:\Program Files\Java\jre7\bin
Hold shift key and right click -> then select Open command window here
After commandline open paste this command
keytool.exe -list -v -keystore "%LocalAppData%\Xamarin\Mono for Android\debug.keystore" -alias androiddebugkey -storepass android -keypass android
Official document here - https://developer.xamarin.com/guides/android/deployment,_testing,_and_metrics/MD5_SHA1/
This questions a few months old, but in the event others were stymied by this and end up here - here's instructions for mac users:
When you use the Android Signing wizard it asks for an alias and password.
Generate the SHA1 by entering by opening a terminal window and entering:
keytool -list -v -keystore /Users/[USERNAME]/Library/Developer/Xamarin/Keystore/[ALIAS]/[ALIAS].keystore -alias [ALIAS]
It will then prompt you for the password and if happy with that, will return certificate info and fingerprints (including the SHA1).
Note two passwords aren't needed as mentioned in the Xamarin documentation here.
(And if like me you were searching in Finder for the keystore file you created with no luck, it's because the Library folder is hidden)
I am a new to android application development. I want to release my app to market. Now I am working in Eclipse. I am stuck at the point of getting a keystore password. How to do this?
Here's an example of a Keytool command that generates a private key:
keytool \
-genkey -v -keystore my-release-key.keystore \
-alias alias_name -keyalg RSA -keysize 2048 -validity 10000
Running the example command above, Keytool prompts you to provide passwords for the keystore and key, and to provide the Distinguished Name fields for your key. It then generates the keystore as a file called my-release-key.keystore. The keystore and key are protected by the passwords you entered. The keystore contains a single key, valid for 10000 days. The alias is a name that you — will use later, to refer to this keystore when signing your application.
For more information about Keytool, see the documentation at this link.
To create keystore refer this link.
You need to sign your app in release mode for that refer this link.
You can see the step by step detailed instructions with screenshots here.
Jsut check the below url
publish app
Compiling and signing with Eclipse ADT When using Eclipse with ADT, you can use the Export Wizard to export a signed .apk (and even create a new keystore, if necessary). The Export Wizard performs all the interaction with the Keytool and Jarsigner for you, which allows you to perform signing via a graphical interface instead of the command-line. Because the Export Wizard uses both Keytool and Jarsigner, you should ensure that they are accessible on your computer, as described above in the Basic Setup for Signing.
To create a signed .apk, right-click the project in the Package Explorer and select Android Tools > Export Signed Application Package. (Alternatively, open your AndroidManifest.xml file in Eclipse, open the Overview tab, and click Use the Export Wizard.) The window that appears will display any errors found while attempting to export your application. If no errors are found, continue with the Export Wizard, which will guide you through the process of signing your application, including steps for selecting the private key with which to sign the .apk, or creating a new keystore and private key.
When you complete the Export Wizard, you'll have a signed .apk that's ready for distribution.
and check below link
Signing Your Applications
Key to Keystore Android from my Windows 10 pro:
Open your command prompt
Type: cd\
Type: cd\
Type:
cd Program Files\Java\jre7\bin>keytool -list -v -keystore "C:\Users\"your username_of_your_pc_login_without_quotes"\.android\debug.keystore" -alias androiddebugkey -storepass android -keypass android
It's my first time that i use Google API. I use it with my Android App by using the beta google java api client. To test my app in the emulator, i took an API Key access from my google account and all work well. But now, what is the procedure about this API Key access if i want share my app in Google Play ? Do I leave my same Key access in the code or in the app, do i must ask final user to register with his own key acces with his google account ? Thank you for answer.
This is simple steps that u need to follow instead of registering it in the site just register the key in Google play .Here is the link example to follow up also follow up with this SO chat u might get some idea click
You should go this path in terminal (cd Library/Android/sdk/platform-tools/) Mac os, after that you can run command below
Create Debug key
keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android
Create Release Key
keytool -list -v -keystore /Users/macbook16/Documents/AndroidProjects/natural-therapy-android/app/keystore.jks -alias myaliassample
Note : /Users/macbook16/Documents/AndroidProjects/natural-therapy-android/app/keystore.jks this path is my project .jks file path, therefore you should replace your project jks file path, And myaliassample is exampl alias, you should replace the command like of your alias