[PR-Keystore-2023] Keystore Google (2023-Now)
In This Article:
Overview
This document will give you explanation about how to fill setup keystore for your project.
Purpose
This SOP was enforced to prevent lost of keystore from necro project that needs to be updated.
Applicability/Scope
This SOP will be used every time the project requires keystore for Google PlayStore.
Prerequisites
This procedure requires access to NAS, lease refer to this guide. The directory access is limited to specific user, if you don’t have access to it please create ticket to IT team.
Responsibilities
- Programmer: create keystore using this procedure
- Devops: support programmer
Procedure
Flow
// todo give flow here
Steps
-
Copy keystore from NAS in:
AgateStudio/Private/Keystore/2023/PKCS12/agate.keystore -
Paste it in your local directory
-
Link it to your engine
-
Unity Project Settings → Player → Publishing Settings
%206b43a3a9897b4136b58a6f8447b2745d/Untitled.png)
-
Unreal
Edit → Project Settings → Platforms - Android → Distribution Signing
%206b43a3a9897b4136b58a6f8447b2745d/Untitled.jpeg)
-
-
Password:
-
Keystore password:
keystore_agatestudio123or you can find it on
AgateStudio/Private/Keystore/2023/Readme.txt -
Use key password value that is registered on keystore:
Alias = agate_keystore Password = keystore_agatestudio123
-
-
to get SHA1 or SHA256, access it on NAS:
AgateStudio/Private/Keystore/2023/PKCS12/export-agate-keystore.txtor you can generate it with CMD command for export certificate to play store (SHA1/SHA256, use the same alias), save key SHA1/SHA256 in the save place
keytool -exportcert -keystore "keystore_path/keystore_name.keystore" -list –v #Full path use double quote (”…”), for example: keytool -exportcert -keystore "D:\Quest\Keystore\agate.keystore" -list –v
- Read full documentation from Google Play Console & Google Console Developer.
Glossary
| Item | Definition |
|---|---|
| NAS | |