Disappearing Key Alias

Solar2D General Questions/Discussion
#1

Hello!

I downloaded the latest public build and when I went to build an Android app, the Key Alias was gone! I’ve attached a screenshot of what the key alias dropdown looks like. For years, I’ve used the same key alias for my personal apps and I did verify the existence of the .keystore on my local machine. 

I also tried using daily build 2016.2999, but that didn’t work either. Is anyone else having these issues? If I’m not able to use the same .keystore, do I lose the ability to update all of my previous apps?

  • Panicked 
#2

If the keystore is on your computer, can’t you just browse and select the appropriate keystore?

#3

I can choose the Keystore, but not the Key alias. I didn’t properly attach my screenshot from before, but here it is. In this, I’ve got my Keystore selected, but I can’t choose a Key Alias.

#4

Is it only happening with this exact keystore or does it happen with all of them like the debug keystore?

#5

Just this keystore.

#6

Have you tried moving the keystore to somewhere else and tried it again? There may be a permissions issue.

Also, can you try this on your keystore and tell if you can see the corresponding alias:

keytool -list -keystore name.keystore
#7

I have moved it, but I moved it to a subfolder. I’ll try moving it back to see if that makes a difference.

For the keytool command, here’s what I’m seeing (I did intentionally 00 out the certificate fingerprint):

Testapp:Google Keystore danielwilliams$ keytool -list -keystore spoggles.keystore

Enter keystore password:  

 

Keystore type: JKS

Keystore provider: SUN

 

Your keystore contains 1 entry

 

spoggles_keystore_for_android, Mar 11, 2011, PrivateKeyEntry, 

Certificate fingerprint (SHA1): FC:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00

Testapp:Google Keystore danielwilliams$ 

#8

Update: When I originally moved the keystore, I moved it to a sub-folder. It was dropbox/Corona SDK/Corona SDK Files. The keystore did not work there.

I moved the keystore back to the original location of dropbox/Corona SDK Files/ and I was able to chose a Key Alias again. Maybe it’s the duplicate folder name that caused the issue here.

#9

And @bgmadclown, thanks for the help!

#10

I’m glad it worked out :slight_smile: Don’t forget to mark your answer solved for future reference :slight_smile:

#11

If the keystore is on your computer, can’t you just browse and select the appropriate keystore?

#12

I can choose the Keystore, but not the Key alias. I didn’t properly attach my screenshot from before, but here it is. In this, I’ve got my Keystore selected, but I can’t choose a Key Alias.

#13

Is it only happening with this exact keystore or does it happen with all of them like the debug keystore?

#14

Just this keystore.

#15

Have you tried moving the keystore to somewhere else and tried it again? There may be a permissions issue.

Also, can you try this on your keystore and tell if you can see the corresponding alias:

keytool -list -keystore name.keystore
#16

I have moved it, but I moved it to a subfolder. I’ll try moving it back to see if that makes a difference.

For the keytool command, here’s what I’m seeing (I did intentionally 00 out the certificate fingerprint):

Testapp:Google Keystore danielwilliams$ keytool -list -keystore spoggles.keystore

Enter keystore password:  

 

Keystore type: JKS

Keystore provider: SUN

 

Your keystore contains 1 entry

 

spoggles_keystore_for_android, Mar 11, 2011, PrivateKeyEntry, 

Certificate fingerprint (SHA1): FC:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00

Testapp:Google Keystore danielwilliams$ 

#17

Update: When I originally moved the keystore, I moved it to a sub-folder. It was dropbox/Corona SDK/Corona SDK Files. The keystore did not work there.

I moved the keystore back to the original location of dropbox/Corona SDK Files/ and I was able to chose a Key Alias again. Maybe it’s the duplicate folder name that caused the issue here.

#18

And @bgmadclown, thanks for the help!

#19

I’m glad it worked out :slight_smile: Don’t forget to mark your answer solved for future reference :slight_smile: