Jump to content

Archived

This topic is now archived and is closed to further replies.

TILK

Signer son appli via la CMD de windows (Help)

Recommended Posts

Bon voilà je touche enfin au but!

Il me reste plus qu'à signer mon application et la mettre sur le market. Malheureusement je bloque sur la signature.

Je fais mon application avec AppInventor de google et voilà l'étape qui ne fonctionne pas chez moi (voir mon image) :

problmesig.jpg

------------------------------------------------------------------------------------------------------

Du tuto que j'ai suivis jusqu'à là :

------------------------------------------------------------------------------------------------------

4) Sign the app and optimize it

From the bin folder of JDK execute in a terminal:

Codice:

jarsigner.exe -verbose -keystore my-release-pre-key.keystore apkname.apk aliasname

You will be prompted to enter your private key password and once entered, the application will be signed with our private key.

------------------------------------------------------------------------------------------------------

De google :

------------------------------------------------------------------------------------------------------

3. Sign your application with your private key

When you have an application package that is ready to be signed, you can do sign it using the Jarsigner tool. Make sure that you have Jarsigner available on your machine, as described in Basic Setup. Also, make sure that the keystore containing your private key is available.

To sign your application, you run Jarsigner, referencing both the application's .apk and the keystore containing the private key with which to sign the .apk. The table below shows the options you could use.

Jarsigner Option Description

-keystore <keystore-name>.keystore The name of the keystore containing your private key.

-verbose Enable verbose output.

-storepass <password>

The password for the keystore.

As a security precaution, do not include this option in your command line unless you are working at a secure computer. If not supplied, Jarsigner prompts you to enter the password. In this way, your password is not stored in your shell history.

-keypass <password>

The password for the private key.

As a security precaution, do not include this option in your command line unless you are working at a secure computer. If not supplied, Jarsigner prompts you to enter the password. In this way, your password is not stored in your shell history.

Here's how you would use Jarsigner to sign an application package called my_application.apk, using the example keystore created above.

$ jarsigner -verbose -keystore my-release-key.keystore

my_application.apk alias_name

Running the example command above, Jarsigner prompts you to provide passwords for the keystore and key. It then modifies the .apk in-place, meaning the .apk is now signed. Note that you can sign an .apk multiple times with different keys.

------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------

Autre petite question : Si je dois mettre à jour l'application, je dois re-rentrer la même clé et si je crée une deuxième application je devrais remettre aussi la même clé?

------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------

Share this post


Link to post
Share on other sites

Si un pro passe par là, si il pouvait m'aidait ce serait chouette!

Voilà mon problème plus en détail :

Dans la CMD je tape cela pour le mener au répertoire où se trouve mon appli en .apk ainsi que mon certificat et les outils java (je cherche à signer mon application avec mon certificat).

PATH = D:\Program Files\Java\jdk1.6.0_23\bin

ET (mes essais de commande)

jarsigner.exe -verbose -keystore my-release-pre-key.keystore Launcher_signed.apk aliasname

jarsigner.exe -verbose -keystore my-release-pre-key.keystore Launcher_signed.apk alias_name

jarsigner.exe -verbose -keystore my-release-key.keystore Launcher_signed.apk aliasname

jarsigner.exe -verbose -keystore my-release-key.keystore Launcher_signed.apk alias_name

Voici le résultat : :emo_im_undecided: (pourquoi?? ça ne marche pas!!!)

problmggg.jpg

Share this post


Link to post
Share on other sites

Cela ne marche pas parce que jarsigner.exe n'est pas ton Path. Soit tu modifies ta variable d'environnement Path pour y inclure le chemin d'accès à jarsigner.exe, soit tu spécifies dans ta ligne de commande le chemin absolu d'accès à jarsigner.exe

Share this post


Link to post
Share on other sites

Oui c'était bien ça le problème, merci :emo_im_kissing: mais j'en rencontre un nouveau juste après avoir rentré la clé de mon certificat...

Ce qui fait que jarsigner n'arrive toujours pas à signer mon application :(

Voilà l'image du message d'erreur :

jarsignerp.jpg

J'ai grand besoin de votre aide. :mad:

Share this post


Link to post
Share on other sites





×
×
  • Create New...