Issue with publishing .aab archive on Google Play:
- or -
Post a project like this$20
- Posted:
- Proposals: 11
- Remote
- #4115356
- Expired
Experienced Full Stack Web and App Developer |Android and IOS App Development| Project Management
London
Web and App Development | Database Expert | Database Analysis| Python Developer
Islamabad
2399376319813235449923790666384821248997848646087976046399552451021796910524075
Description
Experience Level: Entry
I am trying to create app signing for my existing app on Google Play, so that I can upload .aab files instead of .apk.
What I have done so far:
* compiled .aab archive with success.
* Having access to my keystore file.
Then, I have also done these steps:
On Google Play:
1. In "App signing" section, select "Use existing app signing key from Java KeyStore"
2. Download the encryption public key
3. Download PEPK tool
On my computer:
4. Store both files in new folder and open up a terminal in that folder (any terminal is fine)
5. Be sure to have Java JDK installed. Also be sure to have an up-to-date version of JDK (from https://www.oracle.com/java/technologies/downloads/)
6. To add Java to Git Bash PATH, use export PATH="/c/Program Files/Android/Android Studio/jre/bin:$PATH". (replace "/c/Program Files/Android/Android Studio/jre/bin" with the actual path, also be sure it ends with /bin dir!)
7. Use java -version in CLI to make sure JDK is found.
8. Verify that the keystore file and the alias are correct. Use the keytool command to list the aliases in the keystore:
keytool -list -v -keystore /path/to/your/newkeystore.keystore
If found, you are being asked for password. Type in the keystore password. If correct, keystore information should be displayed in CLI.
9. Use the following command:
java -jar pepk.jar --keystore=foo.keystore --alias=foo --output=encrypted_private_key_path --rsa-aes-encryption --encryption-key-path=/path/to/encryption_public_key.pem
I replaced the above placeholder information with that of my own.
Please see attached screenshots for the errors I get.
I have tried it on 2 different computers, I get the same error on both.
It is important you have good communication skills. Please READ carefully this job description before replying. Asking me questions like "do you have a keystore file," etc. shows me you have not bothered to read carefully.
What I have done so far:
* compiled .aab archive with success.
* Having access to my keystore file.
Then, I have also done these steps:
On Google Play:
1. In "App signing" section, select "Use existing app signing key from Java KeyStore"
2. Download the encryption public key
3. Download PEPK tool
On my computer:
4. Store both files in new folder and open up a terminal in that folder (any terminal is fine)
5. Be sure to have Java JDK installed. Also be sure to have an up-to-date version of JDK (from https://www.oracle.com/java/technologies/downloads/)
6. To add Java to Git Bash PATH, use export PATH="/c/Program Files/Android/Android Studio/jre/bin:$PATH". (replace "/c/Program Files/Android/Android Studio/jre/bin" with the actual path, also be sure it ends with /bin dir!)
7. Use java -version in CLI to make sure JDK is found.
8. Verify that the keystore file and the alias are correct. Use the keytool command to list the aliases in the keystore:
keytool -list -v -keystore /path/to/your/newkeystore.keystore
If found, you are being asked for password. Type in the keystore password. If correct, keystore information should be displayed in CLI.
9. Use the following command:
java -jar pepk.jar --keystore=foo.keystore --alias=foo --output=encrypted_private_key_path --rsa-aes-encryption --encryption-key-path=/path/to/encryption_public_key.pem
I replaced the above placeholder information with that of my own.
Please see attached screenshots for the errors I get.
I have tried it on 2 different computers, I get the same error on both.
It is important you have good communication skills. Please READ carefully this job description before replying. Asking me questions like "do you have a keystore file," etc. shows me you have not bothered to read carefully.
Fredrik P.
100% (53)Projects Completed
71
Freelancers worked with
48
Projects awarded
30%
Last project
29 Mar 2024
Sweden
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies