Key Alias always changes to empty after a few days of usage

Solar2D General Questions/Discussion
#1

Hi guys

I have noticed that my Key Alias always changes to empty a few days of use in my laptop. And if I press the dropdown arrow, it pops up ‘The password for the Key Stored located at …Corona SDK\Resources\debug.keystore was not valid, or the key Store was not valid.’ If I try to type in my password, it doesn’t work and says password is wrong.

I am developping my app using two computers, a laptop and a desktop. The desktop is fixed at home and doesn’t seem to have this problem. The laptop is always carried arround. I used it at home, at work and in my friend’s place.

I am really frustrated by this problem. Sometimes if I re-install the simulater, it solves. But recently, event I re-install, it doesnt work.

Can anyone advise me on this please?

#2

Are you saying your debug.keystore is going missing?  Do you have some kind of anti-virus program running that might be quarantining the file?

#3

Another set of questions Please tell us (in other thread preferably):

  • OS Version(s) and number: Ex OSX 10.10.4 or Windows 7 Premium, etc.
  • Corona Version(s): ex: Ver 2015.2687
  • Java Version you made and are making keystores with:  Ex: JDK1.8.045
#4

Java™ SE Runtime Environment (build 1.7.0_79-b15)

Java HotSpot™ 64-Bit Server VM (build 24.79-b02, mixed mode)

OSX 10.11 El Capitan

Corona SDK Version 2015.2696 (2015.8.14)

#5

The debug.keystore seems to be in place. But I need to check my laptop at work, because I am using my home PC which is working fine.

I remembered I have Java JDK 7 or 8. Windows 7 Enterprise.

I will update this once I get to work and start to use the laptop.

Another strange issue is, when I try to deauthorise and log in using another account on my laptop. It keeps saying I am already using that accout with 2 computers. Please deauthorize first in one computer and then log on. Problem is I am only using my home PC and my laptop. These are 2 computers. Why when I am trying to log on my laptop, it says already 2 computers?

#6

Hey there,

I’m having similar issues. My Key Alias drop-down is empty for both Debug and Google Play Keystores. I’ve getting the following error message in the terminal:

Using java version “1.6.0_65”

Java™ SE Runtime Environment (build 1.6.0_65-b14-468-11M4833)

Java HotSpot™ 64-Bit Server VM (build 20.65-b04-468, mixed mode)

sed: RE error: illegal byte sequence

Corona Build: 2015.2755

OS X El Capitan (10.11)

Any help would be hugely appreciated :slight_smile:

#7

Are you saying your debug.keystore is going missing?  Do you have some kind of anti-virus program running that might be quarantining the file?

#8

Another set of questions Please tell us (in other thread preferably):

  • OS Version(s) and number: Ex OSX 10.10.4 or Windows 7 Premium, etc.
  • Corona Version(s): ex: Ver 2015.2687
  • Java Version you made and are making keystores with:  Ex: JDK1.8.045
#9

Java™ SE Runtime Environment (build 1.7.0_79-b15)

Java HotSpot™ 64-Bit Server VM (build 24.79-b02, mixed mode)

OSX 10.11 El Capitan

Corona SDK Version 2015.2696 (2015.8.14)

#10

The debug.keystore seems to be in place. But I need to check my laptop at work, because I am using my home PC which is working fine.

I remembered I have Java JDK 7 or 8. Windows 7 Enterprise.

I will update this once I get to work and start to use the laptop.

Another strange issue is, when I try to deauthorise and log in using another account on my laptop. It keeps saying I am already using that accout with 2 computers. Please deauthorize first in one computer and then log on. Problem is I am only using my home PC and my laptop. These are 2 computers. Why when I am trying to log on my laptop, it says already 2 computers?

#11

hi! got same problem today. key alias is empty, i can’t build the apk.

-Using java version “1.8.0_45” Java™ SE Runtime Environment (build 1.8.0_45-b14) Java HotSpot™ 64-Bit Server VM (build 25.45-b02, mixed mode)

-OS X Yosemite 10.10.5

-Corona 2015.2777

did anybody get luck with solving the problem?

#12

@daviddiligent  please post your Corona Console log after opening the Android Build dialog

@Andrzej Futuretro  you need to update your Corona Simulator to a newer version (the issue you describe was fixed in Daily Build CoronaSDK 2015.2767 but you can just update to the latest Daily Build)

@rustam  please post your Corona Console log after opening the Android Build dialog

Note that problems with Android keystores on OS X and Windows are almost certainly caused by different issues as they are handled in completely different ways on each platform.  We recently had to change the way we do it on OS X to support 10.11 and that introduced an issue with computers whose primary language isn’t English which was fixed in CoronaSDK 2015.2767

#13

Hey there,

I’m having similar issues. My Key Alias drop-down is empty for both Debug and Google Play Keystores. I’ve getting the following error message in the terminal:

Using java version “1.6.0_65”

Java™ SE Runtime Environment (build 1.6.0_65-b14-468-11M4833)

Java HotSpot™ 64-Bit Server VM (build 20.65-b04-468, mixed mode)

sed: RE error: illegal byte sequence

Corona Build: 2015.2755

OS X El Capitan (10.11)

Any help would be hugely appreciated :slight_smile:

#14

hi! got same problem today. key alias is empty, i can’t build the apk.

-Using java version “1.8.0_45” Java™ SE Runtime Environment (build 1.8.0_45-b14) Java HotSpot™ 64-Bit Server VM (build 25.45-b02, mixed mode)

-OS X Yosemite 10.10.5

-Corona 2015.2777

did anybody get luck with solving the problem?

#15

@daviddiligent  please post your Corona Console log after opening the Android Build dialog

@Andrzej Futuretro  you need to update your Corona Simulator to a newer version (the issue you describe was fixed in Daily Build CoronaSDK 2015.2767 but you can just update to the latest Daily Build)

@rustam  please post your Corona Console log after opening the Android Build dialog

Note that problems with Android keystores on OS X and Windows are almost certainly caused by different issues as they are handled in completely different ways on each platform.  We recently had to change the way we do it on OS X to support 10.11 and that introduced an issue with computers whose primary language isn’t English which was fixed in CoronaSDK 2015.2767