Java.lang. Exception: The key store file does not exist: key store error message

When an exception as shown in the figure occurs, do not worry. Go to drive C to check whether the debug.keystore file is generated. If no debug.keystore file is generated, perform the following steps

① Open CMD in the terminal tool and enter:

keytool -genkey -v -keystore debug.keystore -alias androiddebugkey -keyalg RSA -validity 10000

② Fill in the registration information, pay attention to the requirements to set the password, the password must be recorded for subsequent use (registration content can be filled at will)

Enter re-enter new password: // Enter the certificate file password again. Enter complete Enter What is your first and last name? What is the name of your organizational unit? [Unknown]: // Enter the name of your organization. Enter What is the name of your organization? [Unknown]: // Enter the name of the organization, enter What is the name of your City or Locality? Enter What is the name of your State or Province? [Unknown]: // Enter the name of the province/city/autonomous region. Enter What is the two-letter country code for this unit? Enter Is CN=XX, OU=XX, O=XX, L=XX, ST=XX, C=XX correct? [no]: // Enter y and Enter Enter key Password for < testAlias > (RETURN if same as keystore password): / / and the certificate file confirmation certificate passwords are the same (HBuilder | HBuilderX requirements) the two codes, return can directlyCopy the code

③ Run the debug.keystore command to check whether the debug.keystore file is generated

Keytool -list -v -keystore test.keystore Enter keystore password: // Enter the password and press EnterCopy the code

The following format information is output:

Keystore type: PKCS12 Keystore provider: SUN Your keystore contains 1 entry Alias name: test Creation date: 2019-10-28 Entry type: PrivateKeyEntry Certificate chain length: 1 Certificate[1]: Owner: CN=Tester, OU=Test, O=Test, L=HD, ST=BJ, C=CN Issuer: CN=Tester, OU=Test, O=Test, L=HD, ST=BJ, C=CN Serial number: 7dd12840 Valid from: Fri Jul 26 20:52:56 CST 2019 until: Sun Jul 02 20:52:56 CST 2119 Certificate fingerprints: MD5: F9:F6:C8:1F:DB:AB:50:14:7D:6F:2C:4F:CE:E6:0A:A5 SHA1: BB:AC:E2:2F:97:3B:18:02:E7:D6:69:A3:7A:28:EF:D2:3F:A3:68:E7 SHA256: 24:11:7D:E7:36:12:BC:FE:AF:2A:6A:24:BD:04:4F:2E:33:E5:2D:41:96:5F:50:4D:74:17:7F:4F:E2:55:EB:26 Signature algorithm name: SHA256withRSA Subject Public Key Algorithm: 2048-bit RSA key Version: Fingerprints: INDICATES that the MD5 fingerprint of the MD5 Certificate (security code MD5). SHA1 Indicates the SHA1 fingerprint of the Certificate (security code SHA1). SHA256 Indicates the SHA256 fingerprint of the Certificate (security code SHA245)Copy the code

When the debug.keystore file is generated in the folder, this indicates success.

⑤ When we fill in the registration information again, an exception appears as shown in the figure: keytool -genkey -v -keystore debug.keystore -alias androiddebugkey -keyalg RSA -validity 10000