Keystore conversion for App Inventor

[M. Hossein Amerkashi]

Since AI now supports publishing directly to Google Play, I'm working on a AppToMarket feature that will convert they keystore that you generated in AppToMarket to AI keystore. This will allow you to use the AppToMarket generated keystore directly from AI.

Watch this thread for updates.

-Hossein.

[M. Hossein Amerkashi]

AppToMarket v2.7 is now released.

Release Note:
v2.7 now allows you to update your keystore with new password and / or alias. This feature allows you to make keystores that you generated using AppToMarket compatible with App Inventor so that you could upload to AI.

[M. Hossein Amerkashi]

And here is the download link: http://code.google.com/p/apptomarket/downloads/list

-Hossein

[M. Hossein Amerkashi]

AppMan,

If you want the final signing to be done by AppToMarket, then you don't really need to covert your keystore to AI compatible keystore.

On the other hand, if you have an app that you signed using AppToMarket and published to Play, and want to make updates, then in that case, you convert your keystore to AI compatible keystore, upload your keystore to AI, update your app in AI, do final packaging in AI which makes your app directly publishable to Play.

Also, I'm not sure what you mean when you say "yet it still is creating a new app and won't 'update' the original"

-Hossein.

On Wed, Aug 1, 2012 at 8:45 PM, AppMan <ahol...@gmail.com> wrote:

Hmm, I seem to be having trouble getting the app to actually 'update' the original app on my phone. I was able to transfer over my .ks, upload it into the new 2.7 App to market, converted it to the android.keystore and then uploaded that to AI. Redownloaded/Packaged the app and signed it through App to market, yet it still is creating a new app and won't 'update' the original.

Any help or suggestions?

[Khalid Natto]

Step 1: Convert key store in v. 2.7
Step 2: Run the app through Apptomarket
Step 3: Upload to AI
Step 4: Download from AI
Step 5: Upload to PLAY STORE

I am going to try use these steps. I will be looking to see if :

1. GOOGLE PLAY ACCEPTS THE UPDATE
2. If AI adds the "_" underline to the title

Stay tuned to the latest twists and turns in the maze we call MIT

BRB

[M. Hossein Amerkashi]

1> Make sure that you first create a backup for your AI keystore (download it from AI).

2> These steps are necessary for your existing apps that keys were generated using AppToMarket and have been published to Google Play

[Khalid Natto]

WALKING THROUGH THE PROCESS

1. Downloaded and archived original AI Keystore

2. Created and uploaded new KEYSTORE to AI using V2.7 converter

3. Packaging new app failed says "Build failed! Error: Your build failed due to an error in the JarSigner stage, not because of an error in your program."

[M. Hossein Amerkashi]

Did you use:
android as new  password
androidkey as new alias
android.keystore as new keystore name

Did you upload to android.keystore AI?

[Khalid Natto]

YES SIR, DIDNT CHANGE IT.  I PROCESSED IT JUST AS IT COMES UP IN THE CONVERTER

[M. Hossein Amerkashi]

hmm, this was tested and should work. I'll give it a try again.
Since now all the keystores have the same alias / password, can you PM me the keystore that you generated? This way I can test it using yours.

-Hossein.

--
 
 

[Khalid Natto]

SENT IT TO YOUR EMAIL

[M. Hossein Amerkashi]

Khalid,

I think you are doing something wrong. Here is what I did.
I took your keystore and saved into a folder. Then in AppToMarket, tab 1, I updated the configuration to point to your keystore (see yourKeystore.jpg). Then I selected Tools | View Cert Info. It shows me that I have wrong credentials.

Next, I took one of my keystores, converted using this utility. Went through same operations, but this time, pointing to my converted keystore (myKeystore.jpg). Then I selected Tools | View Cert Info. It can access and show cert info properly.

--
 
 

[Khalid Natto]

Ok

This time I made an exact copy of your keystore, and I still got an error message from APPTOMARKET

10Aug2012_1719.17:  Signing the application...

 10Aug2012_1719.17:  jarsigner error: java.lang.RuntimeException: keystore load: Keystore was tampered with, or password was incorrect

 10Aug2012_1719.17:  ERROR: There was error in signing your app

[Khalid Natto]

I uploaded the new android keystore to AI and tried to BUILD

Build failed! Sorry, project was too large to package (2305951 bytes) 

[Khalid Natto]

Status Quo:

1. I am using your identical KEYSTORE

2. APPINVENTOR is alternating between the two error messages

3. I cant build anything unless I use the original APPINVENTOR Keystore

My thoughts are as follows:

1. What are he risks of having a keystore that is identical to everybody else on APPTOMARKET?

2. Can MIT give us an OPT OUT feature with regards to using their SIGNATURE and KEY STORE (Revert to old format)?

3. I prefer version 2.6 and the old MIT format for both security and consistency with updating google play

[M. Hossein Amerkashi]

Khalid,

I didn't send you my keystore :o)    So, don't know how you made copy of my keystore.

-Hossein.

--
 
 

[M. Hossein Amerkashi]

Khalid,

Based on our conversation and the AppToMarket keystore that you sent me, I used AppToMarket and tried to convert it. It seemed like that you initially tried, but did not change alias, then retried it again and this was causing the issue. At any rate. I converted your keystore to AI compatible keystore. It generated a new file called android.keystore for me with alias and password that AI expects. From there, in AppToMarket, from the menu, I selected Tools | View Cert Info (make sure tab 1 has your new password / alias). It was able to successfully access keystore and view cert info.

To test, I uploaded this new keystore into AI, tried to package one of my sample apps, and AI gave signing exception!
I noticed that there was a new release of AI on August 6th (4 days ago). Not sure something has changed, because this process was tested before and worked.

Hal - Do you know why AI gives jarSigner exception when:
keystore has the name that AI expects: android.keystore
has the expected alias: androidkey
has the expected password: android

I have attached a sample converted keystore.

THANKS

[Jeffrey Schiller]

I uploaded your keystore and was able to build a project. So I'm not sure what the next step is. The update on August 6th didn't touch anything near the signing code!

Why don't you try again. If/When it fails, take down the exact time and send me a note. I'll then grovel over the buildserver logs to see if I can find a hint.

-Jeff

[M. Hossein Amerkashi]

Jeff,

Thank you so much for looking into this.

You must've done magic! Its working:
same exact process tried: it worked
created new AppToMarket keystore, converted to AI compatible; uploaded to AI, packaged app: it worked
testing with existing app: it worked
tested with new app: it worked

Thank you again and thanks MIT AI Team

Khalid: Try again. Everything is working.

-Hossein.

--
For Java Bridge (sdkBridger), visit http://code.google.com/p/apptomarket/
---
You received this message because you are subscribed to the Google Groups "AppToMarket" group.
Visit this group at http://groups.google.com/group/apptomarket?hl=en.
 
 

[Khalid Natto]

Build failed! Sorry, project was too large to package (2305947 bytes) 

TRIED AGAIN

16:42 HOURS KSA time

August 11th, 2012

I used the ANDROID.KEYSTORE file that you provided

after that generated that error

I also tried generating ad creating a new Android.keystore

I get the same error message

I think we need a video tutorial.

[M. Hossein Amerkashi]

Khalid,
I just tried again with a converted key and it works fine.
The problem that you are seeing is not related to keystore.

-Hossein

[M. Hossein Amerkashi]

....also IF you want, you can PM me your source and I'll try it out.

-Hossein.

[Khalid Natto]

https://play.google.com/store/apps/details?id=appinventor.ai_khalid.TNP_The_Natto_Perspective 

Here is the app on Google Play

When I try to repackage the AI with the new Keystore you provided me it wont download 

Build failed! Sorry, project was too large to package (2305947 bytes)  

However when I use the original AI Keystore it does download. The problem is that I wont be able to update on Play store

Let me make a video to show you brb

[Khalid Natto]

Ok I have attached a video demonstrating everything from :

1. DOWNLOADING KEYSTORE

2. UPLOADING KEYSTORE

3. LAUNCHING AI

4. FAILED ATTEMPT TO PRODUCE AND BUILD NEW APP

PLEASE KEEP IN MIND THAT ITS THE IDENTICAL APP THAT I HAVE ON GOOGLE PLAY 

Please note that the AI does build it when its using its original keystore

Thank you

[M. Hossein Amerkashi]

Khalid,

When you get the error, you should also click on (Debugging) and see if log prints any useful info.

[The KIN Consortium]

I will try again in a few hours.  I have a series of back to back meetings

[Khalid Natto]

IT WORKED

NOW WE ONLY HAVE THE ISSUE OF THE UNDERLINE BETWEEN THE WORDS

Suggestions please?

[kkas...@gmail.com]

So, what did you do differently this time to have it work?

Also, I dont know what the issue of underline is.

Sent from my HTC on the Now Network from Sprint!

[Khalid Natto]

I just kept trying again and again and it finally downloaded using your KEYSTORE

Regarding the UNDERLINE between the words,  App to Market allows us to delete the Underline and use regular spaces, while AI forces the underline

[M. Hossein Amerkashi]

Please see AI issue list HERE

On Wed, Aug 15, 2012 at 10:39 PM, Khalid Natto <kha...@kinconsortium.com> wrote:

Gentlemen do we have a workaround solution for the UNDERSCORE in the title of the application?

[Khalid Natto]

We did it.  

YOUR INSTRUCTIONS ARE PERFECT

I FOLLOWED THEM AND EVERYTHING WORKED.

IT WORKED AFTER REPETITION  I LITERALLY FOLLOWED THE SAME STEPS...THRILLED AT THE MOMENT

I WILL RETRACE MY STEPS LATER

FOR NOW I JUST CLEARED OUT THE KEYSTORE FILES AND THE RESOURCE CONFIG FILE AND JUST STARTED FRESH 

THANK YOU GENTLEMEN FOR BOTH YOUR ASSISTANCE AND PATIENCE

[Trevor]

Hossein,

I'm also having a similar issue. I'm hoping you can give me some guidance.I'm using AppToMarket v3.2 When I view the cert for the keystore I've been using on AppToMarket everything looks great. However, when I update the keystore to use in AI I get the following error "21May2014_1927.01:  keytool error: java.io.IOException: Keystore was tampered with, or password was incorrect". When I view the cert for this AI compatible keystore I see the following:

21May2014_1934.06:  keytool error: java.io.IOException: Keystore was tampered with, or password was incorrect

21May2014_1934.06:  java.io.IOException: Keystore was tampered with, or password was incorrect

21May2014_1934.06:   at sun.security.provider.JavaKeyStore.engineLoad(Unknown Source)

21May2014_1934.06:   at sun.security.provider.JavaKeyStore$JKS.engineLoad(Unknown Source)

21May2014_1934.06:   at java.security.KeyStore.load(Unknown Source)

21May2014_1934.06:   at sun.security.tools.KeyTool.doCommands(Unknown Source)

21May2014_1934.06:   at sun.security.tools.KeyTool.run(Unknown Source)

21May2014_1934.06:   at sun.security.tools.KeyTool.main(Unknown Source)

21May2014_1934.06:  Caused by: java.security.UnrecoverableKeyException: Password verification failed

21May2014_1934.06:   ... 6 more

Any help you can give would be much appreciated. I am willingly to send my original keystore if you think that will help.

Thanks,

Trevor

[M. Hossein Amerkashi]

This means the alias / password that you are using is not correct. 

--
For Java Bridge (sdkBridger), visit http://code.google.com/p/apptomarket/
---
You received this message because you are subscribed to the Google Groups "AppToMarket" group.

To unsubscribe from this group and stop receiving emails from it, send an email to apptomarket...@googlegroups.com.
Visit this group at http://groups.google.com/group/apptomarket.
For more options, visit https://groups.google.com/d/optout.

[Vipul Chaudhary]

Hi sir I've a .ks File genereated through App To Market two-three years ago. The app is published in the play store.Now i want update it.How can i convert the .ks to .keystore . Please give me alive link for that tool.Thanks..

[Vipul Chaudhary]

I renamed the .ky file and uploaded it to AI.Error while building the app.The logs are as under.

App Inventor is unable to compile this project. 
The compiler error output was 
________Preparing application icon
________Creating animation xml
________Generating manifest file
________Attaching native libraries
________Attaching component assets
________Compiling source files
(compiling appinventor/ai_palanpur/Unit_Convertor_All_Togather/Screen1.yail to appinventor.ai_palanpur.Unit_Convertor_All_Togather.Screen1)
(compiling /tmp/runtime2195502769996032972.scm to com.google.youngandroid.runtime)
Kawa compile time: 2.805 seconds
________Invoking DX
DX time: 4.431 seconds
________Invoking AAPT
AAPT time: 0.052 seconds
________Invoking ApkBuilder
________Signing the apk file

YAIL compiler - jarsigner execution failed. 

[Hossein Amerkashi]

AppToMarket can be used for that. See here:

http://community.appybuilder.com/t/elements-of-new-screen-are-dwarfed/699/44

To unsubscribe from this group and stop receiving emails from it, send an email to apptomarket+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/apptomarket.