Daily build 2750 (or later)
Corona Simulator “Build for Android” window shows like:
“Key Alias:” menu contains nothing. (expected “androiddebugkey”)
“Build” button is not enabled.
For the same project, same settings, daily build 2747 works fine.
So I think this is not keystore problem.
I tried new debug keystore, but things not changed.
OS X 10.11.1 (15B42)
ye I’ve got same problem like you.
there is not any problem with old version.
Please PM me the _ complete _ Corona Console log for a session when this happens.
Also, what is the result of running this command in a Terminal:
which keytool
Also, you might try the most recent Daily Build as there have been some fixes in this area recently.
I have same problem with recent version 2765.
when I choose key store and type password there is nothing appeared key alias.
terminal say nothing.
When I choose keystore Debug. there is not appeared key alias section too. very weird
I think that there is no problem with me because I don’t have any problem with a little old version.
What happens when you hit browse button and navigate to the keystore in /Applications/CoronaSDK-2765/Resource Library/Android/debug.keystore?
And can you try Daily Build 2766 or higher (when it becomes available)? I realized that some error messages from the system might not be making it into the Corona Console and they would shed some light on this situation.
I choose debug.keystore you mention, I need to type password.
It’s very strange. debug.keystore with password? anyway I cannot find Key Alias at this time.
sorry I cannot find version 2766, 2765 is latest version I can find.
2766 should be available sometime over night (early morning) here in the United States.
thanks, I would wait for that version. I hope that version has a solution of problem I’ve got.
The new version isn’t going to solve your issue, but the better debugging might help us figure it out.
The password for the debug keystore should be: android
Rob
I’m sorry to hear that.
I think password for Debug doesn’t care to me.
I have a same issue with “android”. besides, I can pass with anything.
I tried 2766, but I got the same result.
I tried the sample project “Clock”, and I got the same result.
2747 is the last version that I can build for Android.
me, too.
it has not been fixed, and terminall say nothing.
strangely, when I choose keystore, it doesn’t request password moreover.
my environment is…
iMac / 2.7 GHz Intel Core i5 / 8GB 1333 MHz DDR3 / AMD Radeon HD 6770M 512 MB
11** 월 **** 09 08:19:08.594** Copyright © 2009-2015 C o r o n a L a b s I n c .
11** 월 **** 09 08:19:08.594** Version: 3.0.0
11** 월 **** 09 08:19:08.594** Build: 2015.2766
11** 월 **** 09 08:19:08.608** Platform: 1280_800 / x86_64 / 10.11.1 / AMD Radeon HD 6770M OpenGL Engine / 2.1 ATI-1.38.3 / 2015.2766
That isn’t a _ complete _ log of an attempted Android build. Can someone who has this issue please post that for a session in which they’re tried to do an Android build with 2766?
To post a complete log:
If you want to PM that to me instead, that’s fine.
Also, what language is your OS X set too? I’m curious about the strange characters in the timestamps of the log fragment you did post.
Can someone with the issue please run this command in a Terminal window and post the results here? The command is all on one line.
/usr/bin/keytool -list -keystore '/Applications/CoronaSDK-2766/Resource Library/Android/debug.keystore' -storepass 'android' -rfcNote to Perry’s request. If you’re like me and rename CoronaSDK-build# to CoronaSDK, then leave the -build# off of the command line above.
Rob
This issue should be fixed in Daily Build 2767 (or later) which will be available tomorrow. Based on the limited information available I determined we were not handling computers whose language was not set to English correctly.
Tipo keystore: JKS
Provider keystore: SUN
Il keystore contiene 1 voce
Nome alias: androiddebugkey
Data di creazione: 16-gen-2010
Tipo di voce: PrivateKeyEntry
Lunghezza catena certificati: 1
Certificato[1]:
-----BEGIN CERTIFICATE-----
MIIB5TCCAU6gAwIBAgIES1I1XjANBgkqhkiG9w0BAQUFADA3MQswCQYDVQQGEwJVUzEQMA4GA1UE
ChMHQW5kcm9pZDEWMBQGA1UEAxMNQW5kcm9pZCBEZWJ1ZzAeFw0xMDAxMTYyMTUzMzRaFw0xMTAx
MTYyMTUzMzRaMDcxCzAJBgNVBAYTAlVTMRAwDgYDVQQKEwdBbmRyb2lkMRYwFAYDVQQDEw1BbmRy
b2lkIERlYnVnMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCWCdNyNCUMWSWtnnQvS9mzpQ0X
4WCZQuqvjzYHThfidKsrwoLOUApNApeUgNBJ6TZpfiCw4dANlT2/o0+yZtpwxb82cSPnXHLxOIOh
T7egc0Rtri49SGGJxTk/HeWoHt2LvNXjNjQiQdYOdL6b9BVeYsjTagxt1L98gN2DvEmEQwIDAQAB
MA0GCSqGSIb3DQEBBQUAA4GBAD4r7H5D5J1Ar+paWXhLgIrEt3GoFvhfQCNeQ6Hdb72sOE8phRrz
wIP1UDMl+gjy+HSyLbHyS1WOb1sqTwD/bUa5hmNkAf+7N6/u6XuWPm/hppuik0X/8IDXDlQ68Fgl
bT1y3uMqF/wQYLtBJVzIUaVj44LYYTsagr42RIXaNawO
-----END CERTIFICATE-----
*******************************************
*******************************************
This is fixed in Daily Build CoronaSDK 2015.2767. The Simulator wasn’t expecting a command line utility like keytool to change it’s output language.