Develop Reference

i have an issue with building appbundle with flutter

i'm trying to prepare my app for publishing to play store, bur while i'm creating the app bundle, this error shows up too many times, i was recreate the keystore but it's failed again,
i want to mention that when i setup keystore it's asks me for keystore password just without keypass
A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
[ ]
> Failed to read key key from store "/Users/ahd/key.jks": Invalid keystore format

I had this issue and it was because of the version of Java I was using. I used the keytool within Android Studio to generate the keystore instead and this fixed the issue for me.
Run flutter doctor -v and look for the "Java binary at:" entry. Then use this path swapping 'java' for 'keytool' to generate your keystore. For example
/Applications/Android\ Studio.app/Contents/jre/jdk/Contents/Home/bin/keytool -genkey -v -keystore ~/key.jks -keyalg RSA -keysize 2048 -validity 10000 -alias key
In my case I also followed the recommendation that popped up at the end of this to migrate to PKCS12 (once again using the keytool in Android Studio).

dreamweaver does create key sign for Android apps?

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

How to generate a keystore to update a published app?

I am quite new to android, this question maybe quite simple. But i do need your help. I am preparing to submit a update to google play now. When i export the android application, there is a keystore selection dialog. But i don't have the keystore. The project was developed by another company before. Now we only have the source code and the google play developer account. After reading the Signing Your Applications, i know i need to generate one. But there is still something i am not sure about this.
The keystore generate command as below:
$ keytool -genkey -v -keystore my-release-key.keystore -alias alias_name -keyalg RSA -keysize 2048 -validity 10000
This is a self-signed certificate. Is this sufficient for me to submit the update? Or need me to generate another one ? if so, then how to do that?
Any suggestion would be much appreciated.

For creating your own Keystore go to C:\Program Files\Java\jdk1.6.0\bin and execute below command
C:\Program Files\Java\jdk1.6.0\bin>keytool -genkey -v -keystore app.keystore -alias app -keyalg RSA -keysize 2048 -validity 300000
It'll created your app.keystore in C:\Program Files\Java\jdk1.6.0\bin directory and by using this keystore you can sign you application. You must keep this keystore safe because of your app next update.
Update: command for generate SHA-1 from your app.keystore
D:>keytool -v -list -alias app -keystore "D:app.keystore" -storepass app -keypass app

Right click to the project --> select Android tools -->Export signed Application package
this bring you to window "Export Android Application"
Complete the rest. this will give you signed apk as well as keystore
You can take help from this link too :https://www.youtube.com/watch?v=IYhJp-jqJyM

You'll need the original keystore, otherwise you won't be able to update the application on the Play Store. Ask the previous developer to give the one he used to sign the application, then save it in the safest place you can think of.

The apk is not properly signed in upgrading Android application

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.

android application public release issue

after finishing my android application development i used the command showing below to get private key, but it shows some errors such as "The Keystore was tampered with or password was in correct"
$ keytool -genkey -v -keystore DEBUG.keystore
-alias alias_name -keyalg RSA -keysize 2048 -validity 10000
Is my problem with DEBUG.keystore?? Should i need to generate another keystore for public release??

Yes, you should definitely generate another key for public release (and keep it in a save place for future updates).
See http://developer.android.com/guide/publishing/app-signing.html#releasemode for details.
EDIT:
If you'r using Eclipse, use the ADT Plugin for Android to create your keyfiles and sign your application.