I created some web pages with html css and jquery, and I want to convert it to Android apps.
so I download android SDK and using Adobe dreamweaver 5.5 to create my apk file.
it was created and i installed on my phone without any problem. but when I want to upload my apk file to android stores I have a message that: program should not be on debug sign.
How can I remove debug sign or create a my own sign?
You just have to create the key with keytool using the command line (in windows : cmd.exe)
Here is the guide how to do it (scroll down to "1. Obtain a suitable private key")
Depends on how you are signing. Command line with Keytool
or Using Android studio. both ways are easy
For android studio I recommend reading here
For the Keytool method its
$ keytool -genkey -v -keystore my-key.keystore -alias alias_name -keyalg RSA -keysize 2048 -validity 10000
Related
I made the application using Ionic Cordova
Now I want to assemble it and suggested that I create a key at the assembly stage.
On the official site it offers to execute the command in the console
$ keytool -genkey -v -keystore MY-RELEASE-
KEY.keystore -alias MY_ALIAS_NAME -keyalg RSA -keysize 2048 -validity 10000
but where exactly should it be performed?
In what directory is the nada?
Do I need to install android SDK or android Studio.
Who had the experience of building applications, tell me how to do everything correctly
Keytool and jarsigner comes with the java jdk. You can run it wherever you want.
The zipalign tool can be found in /path/to/Android/sdk/build-tools/VERSION/zipalign. For example, on OS X with Android Studio installed, zipalign is in ~/Library/Android/sdk/build-tools/VERSION/zipalign
Just follow everything here. Of course you need JDK
https://ionicframework.com/docs/v1/guide/publishing.html
My app is compiling ok from cloud for iOS Release (not debug)
When I'm trying to do the same for Android, I get the "Invalid Filename" error, just after asking for the password of my certificate which I have previously created :
keytool -genkey -v -keystore release.keystore -alias Selector -keyalg RSA -keysize 2048 -validity 10000
I don't know if any correlation between the app names and the command is needed. As a matter of fact, I'm not sure at all if the error is really related with the certificate.
Any idea?
Now working, don't know how, I think it was the perfect storm between Typescript not compiling properly to JS, Graggle not working fine etc...
Followed some guides but I cannot get it quite right. I will show you the process below that does not make it quite work.
First of all I started off by acquiring an API-key on google console and i put that into my project.
I acquired the sha 1 by typing this into the terminal:
keytool -list -v -keystore ~/.local/share/Xamarin/Mono\ for\ Android/debug.keystore -alias androiddebugkey -storepass android -keypass android
The map now runs smoothly and fine in my xamarin project when I run it on my device.
Then when I try to upload the project I create a keystore named: "myproject.keystore" and I give it the Alias and password: "myproject" as well.
Just like this:
$ keytool -genkey -v -keystore myproject.keystore -alias myproject -keyalg RSA -keysize 2048 -validity 10000
When I now upload the app to google play and it gets accepted I cannot see the map.
Try comparing your project settings between DEBUG and RELEASE to find a difference. Or check for any hard coded API keys or anything that that would be different between the two environments.
Edit:
So after your myproject.keystore is created, you need to extract the SHA-1 from that keystore and add that to the Credential list in Google.
So if you created your myproject.keystore in ~/Users/Someone/Desktop/, then you would extract the keystore the same way you did with the DEBUG version:
keytool -list -v -keystore ~/Users/Someone/Desktop/myproject.keystore
That should give you the second SHA-1 that you need to add to the Google site.
I am developing a PhoneGap application through Eclipse on the Android platform. My code is ready and run perfectly.
Now, I already created a signed APK file in release mode. So, when I uploaded this keystore file on "build.phonegap.com", and clicked on Submit key, I got an error like this:
Error: extension did not match expected (keystore)"
I don't know what is going wrong in this. Is there a proper solution?
A command-line solution:
keytool -genkey -v -keystore yourappname.keystore -alias appnamealias -keyalg RSA -keysize 2048 -validity 10000
According to: This Post
When you are creating your keystore file in Eclipse make sure to manually set the file extension to ".keystore" - instead of the default file name with no extension.
What tools do we need to develop an Android keystore file?
The Android keystore file can be created in the Java Development Kit (JDK), and to download the installation file, click on this link: Install JDK.
How do we create the Android keystore file?
Standard procedure: First you need to open the command prompt as administrator
To go from a directory to its parent directory, write cd.. (push the Enter button). Keep doing it until you reach c:>.
When you are at c:/, write cd Program files (push the Enter button).
cd Java (push the Enter button).
cd jdk1.7.0_03 (push the Enter button).
cd bin (push the Enter button).
**keytool -genkey -v -keystore Your_personal_file_title.keystore -alias Your_personal_alias -keyalg RSA -keysize 2048 -validity 10000** (push the Enter button).
Remember to edit the two text file Your_personal_file_title and Your_personal_alias.
And enter your profile information.
Afterwards it will create your Android keystore file in your C:\Program files\Java\jdk1.7.0_03\bin directory, with the name you gave it…
You now have your keystore file and can activate it in whatever application you generate your Android apps in (for example, build.phonegap.com).
Please remember to use CMD as administrator.
You need to create your own .keystore file. To do this:
Open CMD
Type:
cd C:\java path\java\jdk7\bin
keytool -genkey -v -keystore yourappname.keystore -alias appnamealias -keyalg RSA -keysize 2048 -validity 10000
After that you will have a new release keystore.
I am upgrading Android application that was previously uploaded to the market.
The algorithm is as follows:
Using Eclipse Android tools I export unsigned application package
Then, I am using the same script as at the 1st uploading:
keytool -genkey -v -keystore almeesoft.keystore -alias almeesoft -keyalg RSA -validity 10000
The script asks for the passcode.
Honestly, I do not remember the passcode that I used the 1st time, so I guess
The application is starting uploading
However, at the and I am getting the message
“The apk is not properly signed”
You must sign the apk with the same private key you used when you first uploaded it. If you do not remember the password then you are out of luck. You will not be able to ever update this application. You will need to upload this as a different application with a unique package name.
You are at big loss if you have forgot your password, signing a apk with different keystore will result in different application on android market.
read this
I was incorrect blaming the problem on the forgotten password. There are 2 scripts one needs to run at the first uploading
1.
keytool -genkey -v -keystore .keystore -alias -keyalg RSA -validity 10000 -keypass -storepass
2.
jarsigner -verbose -keystore .keystore .apk -keypass -storepass
The generated file .keystore should be saved.
On the 2nd uploading (updating) only the 2nd (!) script should be run using the same *.keystore file.