4 Replies Latest reply on Oct 7, 2017 1:46 AM by martinb77004568

    Unlock key `KeyName` bug

    CliffBurton

      I accidentally misspelled the "chertificate password" or "keystore password" in the Unlock Key section of the Android version where there is written "This key will be unlocked for one hour".

      Then, for the next hour, I was unable to re-insert the password and locked with the error saying the passwords were wrong.

       

      Shouldn't be there the ability to reinsert the passwords if wrong?

       

      Side-Note: I only noticed it in the Android section but I suppose the same happens in the iOS and Windows Phone sections too.

        • 1. Re: Unlock key `KeyName` bug
          martinb77004568 Level 2

          In the top bar, click on your avatar (on the right) and then "Edit account". Now, click on "Signing keys". Here, you can lock your key. When un-locking it again, you can enter the correct password. You can also delete your keys here in case you don't need it anymore.

          • 2. Re: Unlock key `KeyName` bug
            jorgem6799748

            I have done what you said, in the settings page figure as unlocked, but then when I rebuild the apk the system again lock the key.

             

            So this is not all that bad, I click on the error message and it takes me to this page with this error: http://docs.build.phonegap.com/en_US/support_failed-builds.md.html#keystore

             

            403 Forbidden

            • Code: AccessDenied
            • Message: Access Denied
            • RequestId: 6E1568AFB50991EA
            • HostId: 6I0S3Bj3VX/FtP/47eqZeTcXiqa300pQeSBxsTPzj057WCUd1x9Nap+T9ppjpU2xx+a3Ua/9vgQ=
            • 3. Re: Unlock key `KeyName` bug
              jorgem6799748 Level 1

              The log errors...

               

              Build Date: 2017-10-06 15:03:58 +0000

              Configuration on demand is an incubating feature.

              :preBuild UP-TO-DATE

              :preReleaseBuild UP-TO-DATE

              :checkReleaseManifest

              :CordovaLib:preBuild UP-TO-DATE

              :CordovaLib:preReleaseBuild UP-TO-DATE

              :CordovaLib:compileReleaseNdk UP-TO-DATE

              :CordovaLib:compileLint

              :CordovaLib:copyReleaseLint UP-TO-DATE

              :CordovaLib:mergeReleaseProguardFiles

              :CordovaLib:packageReleaseRenderscript UP-TO-DATE

              :CordovaLib:checkReleaseManifest

              :CordovaLib:prepareReleaseDependencies

              :CordovaLib:compileReleaseRenderscript

              :CordovaLib:generateReleaseResValues

              :CordovaLib:generateReleaseResources

              :CordovaLib:packageReleaseResources

              :CordovaLib:compileReleaseAidl

              :CordovaLib:generateReleaseBuildConfig

              :CordovaLib:generateReleaseAssets UP-TO-DATE

              :CordovaLib:mergeReleaseAssets

              :CordovaLib:processReleaseManifest

              :CordovaLib:processReleaseResources

              :CordovaLib:generateReleaseSources

              :CordovaLib:compileReleaseJavaWithJavacNote: Some input files use or override a deprecated API.

              Note: Recompile with -Xlint:deprecation for details.

               

              :CordovaLib:processReleaseJavaRes UP-TO-DATE

              :CordovaLib:transformResourcesWithMergeJavaResForRelease

              :CordovaLib:transformClassesAndResourcesWithSyncLibJarsForRelease

              :CordovaLib:mergeReleaseJniLibFolders

              :CordovaLib:transformNative_libsWithMergeJniLibsForRelease

              :CordovaLib:transformNative_libsWithSyncJniLibsForRelease

              :CordovaLib:bundleRelease

              :prepareProjectCordovaLibUnspecifiedReleaseLibrary

              :prepareReleaseDependencies

              :compileReleaseAidl

              :compileReleaseRenderscript

              :generateReleaseBuildConfig

              :generateReleaseAssets UP-TO-DATE

              :mergeReleaseAssets

              :generateReleaseResValues

              :generateReleaseResources

              :mergeReleaseResources

              :processReleaseManifest

              :processReleaseResources

              :generateReleaseSources

              :compileReleaseJavaWithJavac

              :compileReleaseNdk UP-TO-DATE

              :compileReleaseSources

              :transformClassesWithDexForRelease

              :mergeReleaseJniLibFolders

              :transformNative_libsWithMergeJniLibsForRelease

              :processReleaseJavaRes UP-TO-DATE

              :transformResourcesWithMergeJavaResForRelease

              :packageRelease

              :assembleRelease

              :cdvBuildRelease

               

              BUILD SUCCESSFUL

               

              Total time: 3.408 secs

              Built the following apk(s):

              /project/build/outputs/apk/project-release-unsigned.apk

              Starting application signing

              jarsigner: key associated with RegionalSeguros not a private key

              Finished application signing

               

              I created my key with this app: https://headjack.io/tutorial/create-android-keystore-file/

              • 4. Re: Unlock key `KeyName` bug
                martinb77004568 Level 2

                Has your key worked before? I don't know the application you mentioned so I would suggest trying this method: Android Signing | PhoneGap Docs

                What does the error message say? Something like "Incorrect password" or "Wrong alias"?

                Anyways: Make sure the alias matches the one in your keystore. Furthermore, check if the password entered is correct.

                Maybe, you are using some characters (in the password or elsewhere) that aren't allowed?