How can i sign APK With Upload Cert
up vote
0
down vote
favorite
i have Enrolled my app in Google's (App signing).
so now i Got a :
1: App signing certificate .der
2: Upload certificate .der
so what now ?
how do i use the UploadCert.der to sign APK and Push update ?
and what do i do with my old SigningKey.jks that i used to sign my app with !
i thought i should use it in Android studio when i generate APK . so that didn't work.
ScreenShot from My Play Console
android 
android-studio 
android-app-signing asked Nov 11 at 2:29
Ali Hussain
32
add a comment |
up vote
0
down vote
favorite
i have Enrolled my app in Google's (App signing).
so now i Got a :
1: App signing certificate .der
2: Upload certificate .der
so what now ?
how do i use the UploadCert.der to sign APK and Push update ?
and what do i do with my old SigningKey.jks that i used to sign my app with !
i thought i should use it in Android studio when i generate APK . so that didn't work.
ScreenShot from My Play Console
android android-studio android-app-signing asked Nov 11 at 2:29
Ali Hussain
32
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
i have Enrolled my app in Google's (App signing).
so now i Got a :
1: App signing certificate .der
2: Upload certificate .der
so what now ?
how do i use the UploadCert.der to sign APK and Push update ?
and what do i do with my old SigningKey.jks that i used to sign my app with !
i thought i should use it in Android studio when i generate APK . so that didn't work.
ScreenShot from My Play Console
android android-studio android-app-signing asked Nov 11 at 2:29
Ali Hussain
32
i have Enrolled my app in Google's (App signing).
so now i Got a :
1: App signing certificate .der
2: Upload certificate .der
so what now ?
how do i use the UploadCert.der to sign APK and Push update ?
and what do i do with my old SigningKey.jks that i used to sign my app with !
i thought i should use it in Android studio when i generate APK . so that didn't work.
ScreenShot from My Play Console
android android-studio android-app-signing android android-studio android-app-signing asked Nov 11 at 2:29
Ali Hussain
32
asked Nov 11 at 2:29
Ali Hussain
32
asked Nov 11 at 2:29
Ali Hussain
32
asked Nov 11 at 2:29
Ali Hussain
32
asked Nov 11 at 2:29
Ali Hussain
32
32
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
You should sign your APKs with the keystore you created when generating the upload certificate you uploaded to Play Console.
Note that the .der files that Play Console allow you to download are only the certificates, they don't contain the private key to sign anything. Although you have uploaded the app signing private key, only you has the upload private key. If you can't find the keystore, you can contact Play support team and ask to regenerate a new upload key.
answered Nov 11 at 4:36
Pierre
1,37667
i have used PEPK Tool to encrypt my .jsk file and output is .pem which i have uploaded to Play console .. so i should use .pem file !
– Ali Hussain
Nov 11 at 6:40
No. The output of PEPK isn't a PEM file, and that was the keystore (.jks) of the app signing key. Based on your screenshot, it looks like you have also created another keystore for the upload key and you must have ran some other command (from keytool) which created a PEM file. Use that second keystore to sign your APK (note: the PEM does not contain your private key so is useless for signing).
– Pierre
Nov 11 at 13:24
i was trying to output .jks but for some reason it didn't work . so i so on online i should use .pem .. so i did .. and it worked .. Play console Accepted it .. so what i tried now .. is just to use my old Signing cert to sign APK and i uploaded it for a test and it worked ! i didn't get any error from Play Console . so now then what's the point of Enrolling in App signing .. im using my old Cert either way !
– Ali Hussain
Nov 11 at 21:07
There are two purposes to App Signing: 1) if you upload an Android App Bundle instead of an APK, Google Play can serve more optimized APKs to the developers. 2) if you lose your "old" keystore, you won't have to recreate a new app because Google will have a copy of it so you can keep updating your app.
– Pierre
Nov 12 at 22:12
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You should sign your APKs with the keystore you created when generating the upload certificate you uploaded to Play Console.
Note that the .der files that Play Console allow you to download are only the certificates, they don't contain the private key to sign anything. Although you have uploaded the app signing private key, only you has the upload private key. If you can't find the keystore, you can contact Play support team and ask to regenerate a new upload key.
answered Nov 11 at 4:36
Pierre
1,37667
i have used PEPK Tool to encrypt my .jsk file and output is .pem which i have uploaded to Play console .. so i should use .pem file !
– Ali Hussain
Nov 11 at 6:40
No. The output of PEPK isn't a PEM file, and that was the keystore (.jks) of the app signing key. Based on your screenshot, it looks like you have also created another keystore for the upload key and you must have ran some other command (from keytool) which created a PEM file. Use that second keystore to sign your APK (note: the PEM does not contain your private key so is useless for signing).
– Pierre
Nov 11 at 13:24
i was trying to output .jks but for some reason it didn't work . so i so on online i should use .pem .. so i did .. and it worked .. Play console Accepted it .. so what i tried now .. is just to use my old Signing cert to sign APK and i uploaded it for a test and it worked ! i didn't get any error from Play Console . so now then what's the point of Enrolling in App signing .. im using my old Cert either way !
– Ali Hussain
Nov 11 at 21:07
There are two purposes to App Signing: 1) if you upload an Android App Bundle instead of an APK, Google Play can serve more optimized APKs to the developers. 2) if you lose your "old" keystore, you won't have to recreate a new app because Google will have a copy of it so you can keep updating your app.
– Pierre
Nov 12 at 22:12
add a comment |
up vote
0
down vote
You should sign your APKs with the keystore you created when generating the upload certificate you uploaded to Play Console.
Note that the .der files that Play Console allow you to download are only the certificates, they don't contain the private key to sign anything. Although you have uploaded the app signing private key, only you has the upload private key. If you can't find the keystore, you can contact Play support team and ask to regenerate a new upload key.
answered Nov 11 at 4:36
Pierre
1,37667
i have used PEPK Tool to encrypt my .jsk file and output is .pem which i have uploaded to Play console .. so i should use .pem file !
– Ali Hussain
Nov 11 at 6:40
No. The output of PEPK isn't a PEM file, and that was the keystore (.jks) of the app signing key. Based on your screenshot, it looks like you have also created another keystore for the upload key and you must have ran some other command (from keytool) which created a PEM file. Use that second keystore to sign your APK (note: the PEM does not contain your private key so is useless for signing).
– Pierre
Nov 11 at 13:24
i was trying to output .jks but for some reason it didn't work . so i so on online i should use .pem .. so i did .. and it worked .. Play console Accepted it .. so what i tried now .. is just to use my old Signing cert to sign APK and i uploaded it for a test and it worked ! i didn't get any error from Play Console . so now then what's the point of Enrolling in App signing .. im using my old Cert either way !
– Ali Hussain
Nov 11 at 21:07
There are two purposes to App Signing: 1) if you upload an Android App Bundle instead of an APK, Google Play can serve more optimized APKs to the developers. 2) if you lose your "old" keystore, you won't have to recreate a new app because Google will have a copy of it so you can keep updating your app.
– Pierre
Nov 12 at 22:12
add a comment |
up vote
0
down vote
up vote
0
down vote
You should sign your APKs with the keystore you created when generating the upload certificate you uploaded to Play Console.
Note that the .der files that Play Console allow you to download are only the certificates, they don't contain the private key to sign anything. Although you have uploaded the app signing private key, only you has the upload private key. If you can't find the keystore, you can contact Play support team and ask to regenerate a new upload key.
answered Nov 11 at 4:36
Pierre
1,37667
You should sign your APKs with the keystore you created when generating the upload certificate you uploaded to Play Console.
Note that the .der files that Play Console allow you to download are only the certificates, they don't contain the private key to sign anything. Although you have uploaded the app signing private key, only you has the upload private key. If you can't find the keystore, you can contact Play support team and ask to regenerate a new upload key.
answered Nov 11 at 4:36
Pierre
1,37667
answered Nov 11 at 4:36
Pierre
1,37667
answered Nov 11 at 4:36
Pierre
1,37667
answered Nov 11 at 4:36
Pierre
1,37667
1,37667
i have used PEPK Tool to encrypt my .jsk file and output is .pem which i have uploaded to Play console .. so i should use .pem file !
– Ali Hussain
Nov 11 at 6:40
No. The output of PEPK isn't a PEM file, and that was the keystore (.jks) of the app signing key. Based on your screenshot, it looks like you have also created another keystore for the upload key and you must have ran some other command (from keytool) which created a PEM file. Use that second keystore to sign your APK (note: the PEM does not contain your private key so is useless for signing).
– Pierre
Nov 11 at 13:24
i was trying to output .jks but for some reason it didn't work . so i so on online i should use .pem .. so i did .. and it worked .. Play console Accepted it .. so what i tried now .. is just to use my old Signing cert to sign APK and i uploaded it for a test and it worked ! i didn't get any error from Play Console . so now then what's the point of Enrolling in App signing .. im using my old Cert either way !
– Ali Hussain
Nov 11 at 21:07
There are two purposes to App Signing: 1) if you upload an Android App Bundle instead of an APK, Google Play can serve more optimized APKs to the developers. 2) if you lose your "old" keystore, you won't have to recreate a new app because Google will have a copy of it so you can keep updating your app.
– Pierre
Nov 12 at 22:12
add a comment |
i have used PEPK Tool to encrypt my .jsk file and output is .pem which i have uploaded to Play console .. so i should use .pem file !
– Ali Hussain
Nov 11 at 6:40
No. The output of PEPK isn't a PEM file, and that was the keystore (.jks) of the app signing key. Based on your screenshot, it looks like you have also created another keystore for the upload key and you must have ran some other command (from keytool) which created a PEM file. Use that second keystore to sign your APK (note: the PEM does not contain your private key so is useless for signing).
– Pierre
Nov 11 at 13:24
i was trying to output .jks but for some reason it didn't work . so i so on online i should use .pem .. so i did .. and it worked .. Play console Accepted it .. so what i tried now .. is just to use my old Signing cert to sign APK and i uploaded it for a test and it worked ! i didn't get any error from Play Console . so now then what's the point of Enrolling in App signing .. im using my old Cert either way !
– Ali Hussain
Nov 11 at 21:07
There are two purposes to App Signing: 1) if you upload an Android App Bundle instead of an APK, Google Play can serve more optimized APKs to the developers. 2) if you lose your "old" keystore, you won't have to recreate a new app because Google will have a copy of it so you can keep updating your app.
– Pierre
Nov 12 at 22:12
i have used PEPK Tool to encrypt my .jsk file and output is .pem which i have uploaded to Play console .. so i should use .pem file !
– Ali Hussain
Nov 11 at 6:40
i have used PEPK Tool to encrypt my .jsk file and output is .pem which i have uploaded to Play console .. so i should use .pem file !
– Ali Hussain
Nov 11 at 6:40
No. The output of PEPK isn't a PEM file, and that was the keystore (.jks) of the app signing key. Based on your screenshot, it looks like you have also created another keystore for the upload key and you must have ran some other command (from keytool) which created a PEM file. Use that second keystore to sign your APK (note: the PEM does not contain your private key so is useless for signing).
– Pierre
Nov 11 at 13:24
No. The output of PEPK isn't a PEM file, and that was the keystore (.jks) of the app signing key. Based on your screenshot, it looks like you have also created another keystore for the upload key and you must have ran some other command (from keytool) which created a PEM file. Use that second keystore to sign your APK (note: the PEM does not contain your private key so is useless for signing).
– Pierre
Nov 11 at 13:24
i was trying to output .jks but for some reason it didn't work . so i so on online i should use .pem .. so i did .. and it worked .. Play console Accepted it .. so what i tried now .. is just to use my old Signing cert to sign APK and i uploaded it for a test and it worked ! i didn't get any error from Play Console . so now then what's the point of Enrolling in App signing .. im using my old Cert either way !
– Ali Hussain
Nov 11 at 21:07
i was trying to output .jks but for some reason it didn't work . so i so on online i should use .pem .. so i did .. and it worked .. Play console Accepted it .. so what i tried now .. is just to use my old Signing cert to sign APK and i uploaded it for a test and it worked ! i didn't get any error from Play Console . so now then what's the point of Enrolling in App signing .. im using my old Cert either way !
– Ali Hussain
Nov 11 at 21:07
There are two purposes to App Signing: 1) if you upload an Android App Bundle instead of an APK, Google Play can serve more optimized APKs to the developers. 2) if you lose your "old" keystore, you won't have to recreate a new app because Google will have a copy of it so you can keep updating your app.
– Pierre
Nov 12 at 22:12
There are two purposes to App Signing: 1) if you upload an Android App Bundle instead of an APK, Google Play can serve more optimized APKs to the developers. 2) if you lose your "old" keystore, you won't have to recreate a new app because Google will have a copy of it so you can keep updating your app.
– Pierre
Nov 12 at 22:12
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53245335%2fhow-can-i-sign-apk-with-upload-cert%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
