pcsoft.us.windevCopyright 2026, PC SOFT3 Jan 2013 07:50:14 Z2 Jan 2013 09:32:54 ZGreetings All, For the past three days I have been on an Odyssey learning about keystores and signing apps in an attempt to get my Map Control to work. Apparently it does not work unless you sign your app AND you provide a valid key that corresponds to the SHA1 print and your Package. I am using the Keytool that comes with Eclipse Juno in the ADT Android SDK Bundle. I am able to create a keystore (.jks) file. But when I reference it during the Android deployment I get the following error: Failure creating the Android application named . Reason: Failure signing the generated Android archive. An error was returned by the tool for archive signature. Possible solutions: - Check the parameters specified in the command line of the tool for archive signature. - Check whether the passwords specified for the key file and for the key are correct. - Generate a new key file (delete the existing key file). (See the error below to define the correction to perform). Command Line: "C:\Program Files\Java\jdk1.7.0_01\in\jarsigner.exe" -keystore "C:\Documents and Settings\Administrator\.android\interrasys-keystore\interrasys3.keystore.jks" -storepass xxxxxxxx -keypass xxxxxxxx -digestalg SHA1 -sigalg SHA1withDSA "MapControlTest.apk" interrasys3 Error returned: jarsigner error: java.security.SignatureException: private key algorithm is not compatible with signature algorithm I found what I think is the solution to the problem at this website: http://www.basic4ppc.com/forum/bugs-wishlist/20383-code-signing-failure-sha1dsa.html So I changed the commands associated with the deployment from this: -keystore "C:\Documents and Settings\Administrator\.android\interrasys-keystore\interrasys3.keystore.jks" -storepass xxxxxxxx -keypass xxxxxxxx -digestalg SHA1 -sigalg SHA1withDSA "MapControlTest.apk" interrasys3 To this: -keystore "C:\Documents and Settings\Administrator\.android\interrasys-keystore\interrasys3.keystore.jks" -storepass xxxxxxxx -keypass xxxxxxxx -digestalg SHA1 -sigalg SHA1withRSA "MapControlTest.apk" interrasys3 Essentially SHA1withDSA becomes SHA1withRSA. After that change, I was able to deploy my app without an error. I also went to https://code.google.com/apis/console/#project:436890519471:access and created a new Android Google key It 'appears' that WinDev Mobile's thinks that you need to provide an MD5 print and it displays your MD5 pring from your signing key in the window when you click 'Get a Key' during the deployment process. It then provides a link (an old link) to get http://code.google.com/android/maps-api-signup.html But then you get re-directed to: https://developers.google.com/maps/documentation/android/ Here I created a new key using my SHA1 print (which is what it seems that they require now along with ';' and the name of my package as: 20:8X:09:71:8X:7C:42:X8:X3:30:X6:43:41:X4:3X:21:2X:5X:AX:X6;com.flytetymelimo.vaa_airport_coordinator_ii And then then I get my new key as: XIzaXyXq0XXXqdbaXX4gG-98_ciphzXXXXmn8XX I use that key for the deployment of my Android map that has a Map Control. My project has code to add two markers. I 'see' the markers, but I only see a grid with the word 'Google' in the lower left corner. I also see a zoom control. Question, please... Does this all seem to make sense? Or am I going about this all wrong? If I saw an error while loading the Map Control then I would know that my key is wrong, right? If I could not deploy the app then I would know that my SHA1 print was wrong, right? By the way...PC-SOFT should change something the following in the Android deployment process. On the page entitled, 'Signature of the application', I think it where it says 'Name of private key:' it should show as 'Alias:'. Because that is what I am using in this field. If I was wrong on that I would think that I would not be able to deploy my app with these credentials. I am still stuck, so if someone can provide some pointers I would really, really appreciate it. Thanks and Happy New Year!! Paul30WEBDEVen_UShttps://forum.pcsoft.fr/fr-FR/pcsoft.us.windev/37985-android-wdm17-keytool-jarsigner-mapcontrol-hell/read.awpmoderateur@pcsoft.fr (Le modérateur)webmaster@pcsoft.fr (Le Webmaster)guestpcsoft.us.windevhttps://forum.pcsoft.fr/fr-FR/pcsoft.us.windev/37985-android-wdm17-keytool-jarsigner-mapcontrol-hell-solved-38007/read.awp3 Jan 2013 07:50:14 ZGreetings All, I just thought I would document the solution for getting the Map Control to work. First of all the solution…https://forum.pcsoft.fr/fr-FR/pcsoft.us.windev/37985-android-wdm17-keytool-jarsigner-mapcontrol-hell-solved-38007/read.awphttps://forum.pcsoft.fr/fr-FR/pcsoft.us.windev/37985-android-wdm17-keytool-jarsigner-mapcontrol-hell-solved-38007/read.awpAndroid-WDM17 - I am in Keytool / Jarsigner / MapControl Hellguestpcsoft.us.windevhttps://forum.pcsoft.fr/fr-FR/pcsoft.us.windev/37985-android-wdm17-keytool-jarsigner-mapcontrol-hell-37988/read.awp2 Jan 2013 09:33:19 ZAll, I am trying to experiment with some different jarsigner parameters... When I change them it creates the .apk file but…https://forum.pcsoft.fr/fr-FR/pcsoft.us.windev/37985-android-wdm17-keytool-jarsigner-mapcontrol-hell-37988/read.awphttps://forum.pcsoft.fr/fr-FR/pcsoft.us.windev/37985-android-wdm17-keytool-jarsigner-mapcontrol-hell-37988/read.awpAndroid-WDM17 - I am in Keytool / Jarsigner / MapControl Hell