KeyStore Generator Tool

[Perry]

That's a browser issue. (IE) just rename it to keystore.zip , and then your fine. Ready to unzip.

[Robotica]

It was getting the same error as simflare... even though I chose the c: drive to write too and also running as Admin.

I simply removed the comma (,) between my State and County and now it finally created a file.

[leewriting]

Does the keystore program from 2013 work with the current Android APK exports?

[Perry]

Does the keystore program from 2013 work with the current Android APK exports?

Yes It does

[King_Cool]

Hi
Im having the same problems as Simflare and KLiK-iT

I think i was using an older version ofthe KeyStoreTool at first ( as the one i have now downloaded from this thread looks different, having spinning nucleus and a gray background ).
- I generated a coupple of file and deleted them ( because i put in some wrong information )
- Then it wouldnt create any more keystore files
- I downloaded the new KeyStoreTool ( the zip file from the first post in this thread )
- Still will not create any new files ( destination is C:, all fields are filled and unique, Alias is 6 characters no spaces or underscores ) although the gray box popps up after i press build and the tool displays the path to the file

Am i doing something wrong, or misunderstandig how this works?
Is there a limit on number of keystore files i can generate?

EDIT: Got it working now, not sure what was the case. #1 I removed any speces from any of the fields, #2 i put it on the desktop

[King_Cool]

Uh, but now i get an error instead:
C:\Program Files (x86)\Android\android-sdk\tools\ant\build.xml:1147: Signing key TEST not found

I moved the file to a new location after creation, and then pointed Fusion to the file.
I can see the file is there in my browser.
Whats wrong?

[Danny]

First of all, are you certain you are running the Generator tool as 'administrator'? Secondly, does it def. create the file? Can you see it upon completion?

Thirdly, ensure you use the Keystore name as the full path file and make sure you use exactly the correct details for that license file.

[King_Cool]

Its solved
Problem was i was confused about what write in 'key name' in Fusions Android properties.
The video toturial ( sticky ) i followed used the same data in many of the fields on the left side of the Keytool, so i guess i wasnt 100% sure what referrances to use in each field.

More specifically i must have missed the fact that the 'Keyname' field in the Fusion Android settings was supposed to referrance the Alias in the Keytool.

Anyway its solved now, and thanks for all the support!

[AwesomeMan]

Thanks man !

[fantasio]

Hello there !

I have a problem with Android 6 and certificates. I use the keystore tool Danny mentionned in the first post to generate my certificates.

Here is the problem: when I am not in release mode, my apps work on Android 6, but when I build a "release mode" one, the applications never launch on Android 6.

Everything works fine with older Android versions and with the same certificates.

I already spoke about this problem with Fernando and he told me this could come from the fact that my certificate needs to be in 64 or 32 bits. However, I don't know how to make a certificate in 64 or 32 bits. Plus, I am not sure if this is the solution I need.