Hi there,
It worked once, even produced a (kinda) working .apk…
The second time I tried to build the same app I found the “Build” button disabled, no matter what I tried to enter in the Build dialog.
Am I missing something obvious or it is just a bug? Is there a work around?
[import]uid: 4369 topic_id: 1925 reply_id: 301925[/import]
OH, YES…
I forgot to choose a key alias from the list.
I can say in my defense that it wasn’t obvious at all 
[import]uid: 4369 topic_id: 1925 reply_id: 5668[/import]
I’m getting the same problem…
But in my case the Key Alias field, which is a dropdown, does not contain any values and I can not populate this field. I was going to use debug.keystore which is included with the SDK. Any clues? [import]uid: 7920 topic_id: 1925 reply_id: 6295[/import]
Same problem. I could see my new keystore but when loaded I couldn’t select alias (even the old debug ‘android’ alias was sometimes there for some reason…hint-bug!).
After approx 3 hour of reading about creating keys I figured I am doing it right.
Anyway, I figured out a solution:
select the new keystore.
restart corona (NOT just close the build screen).
enter keystore password.
restart corona.
select alias.
Build.
[import]uid: 4294 topic_id: 1925 reply_id: 6520[/import]
@kreso: What version of corona are you using when you see that issue? the GE beta? or the normal sdk (2010.09.16) [import]uid: 3 topic_id: 1925 reply_id: 6562[/import]
I use the normal sdk (2010.09.16)
EDIT: first time I used SKD, debugkey loaded perfectly. This time I wanted to use my own key and that is when this happened. [import]uid: 4294 topic_id: 1925 reply_id: 6602[/import]
Same here. But my problem is with the debug key. I use normal edition. The game edition works fine though. The problem is the same, which is no key alias in the drop down box for me to select. [import]uid: 5976 topic_id: 1925 reply_id: 6660[/import]
When you problem shows up have you just picked the key file? or just typed the password for it?
[import]uid: 3 topic_id: 1925 reply_id: 6701[/import]
I typed the password for the key already, which is “android”, according to the website. Usually, I would be able to see an option inside the drop-down list. But with normal edition, there was nothing in there and I couldn’t choose anything. [import]uid: 5976 topic_id: 1925 reply_id: 6702[/import]
Same problem. I downloaded corona SDK, started going through the 5 minute thing. I tried to build for android, selected debug.keystore, use “android” as password. I dont get any errors but I am not able to select anything from the alias dropdown.
The build button remains grayed out, inactive, mocking me. I feel sad.
*update* I’ve created my own key and still cannot choose from the “choose alias” dropdown and still cannot build. Perhaps this feature is disabled for the trial? [import]uid: 9562 topic_id: 1925 reply_id: 6792[/import]
Is there any output in the terminal when this happens to you guys? (you need to open corona via corona terminal to see output)
Can you guys send me (support @ anscamobile dot com) a copy of the terminal output? [import]uid: 3 topic_id: 1925 reply_id: 6795[/import]
I’ve seen this issue but have not been able to reliably reproduce. One possible work-around, as kreso reported earlier in this thread (http://developer.anscamobile.com/forum/2010/09/07/cant-build-android-build-button-disabled#comment-6520), is to select your new keystore file in one Corona session, restart Corona, and then enter your password for the keystore in the second session. This has also worked for me once.
As a last resort, clear the Simulator’s preferences: quit Corona, delete ~/Library/Preferences/com.anscamobile.Corona_Simulator.plist, and restart. Go through the motions again: enter the build information, select your keystore file, and enter your password when prompted. This may also get you into a working state.
I opened case 1283 to better track the issue. Thanks for your patience.
Tim [import]uid: 8196 topic_id: 1925 reply_id: 6798[/import]
That worked (select keystore, restart, select alias and enter password). Sorry, when I read that older message I was not trying to use my own keystore and when I started trying to use my own keystore, I forgot about the message. 
[import]uid: 9562 topic_id: 1925 reply_id: 6799[/import]