简体   繁体   English

Google Play Console 新的应用签名流程:我们每次发布应用时都需要 .pepk 和 .keystore 文件吗?

[英]Google Play Console New App Signing Process: Do we need .pepk and .keystore files both everytime when we release the app?

I am planning to upload a brand new app to the Google Play Store.我计划将一个全新的应用程序上传到 Google Play 商店。

I have followed this link to generate .aab file.我已按照此链接生成 .aab 文件。 https://developer.android.com/studio/publish/app-signing#sign_release https://developer.android.com/studio/publish/app-signing#sign_release

在此处输入图片说明

.pepk, KeyStore, .aab files generated. .pepk、KeyStore、.aab 文件生成。

在此处输入图片说明

Now I have selected the first option("Let Google manage and protect your app signing key") in Google Play Console for the app signing and uploaded the .aab file.现在,我在 Google Play Console 中选择了第一个选项(“让 Google 管理和保护您的应用签名密钥”)进行应用签名并上传了 .aab 文件。

I am not sure whether this is the correct way of uploading the .aab file because it never asked me to upload the .pepk file.我不确定这是否是上传 .aab 文件的正确方法,因为它从未要求我上传 .pepk 文件。 However .aab file uploaded successfully.但是 .aab 文件上传成功。

I guess I don't need to generate .pepk file from Android Studio if I go with the option "Let Google manage and protect your app signing key"如果我选择“让 Google 管理和保护您的应用签名密钥”,我想我不需要从 Android Studio 生成 .pepk 文件

在此处输入图片说明

So hereafter do I need to use both .pepk and .keystore files to sign the .aab file?那么此后我是否需要同时使用 .pepk 和 .keystore 文件来签署 .aab 文件? What happens if I lose any of the two or both?如果我失去了两者中的任何一个或两者,会发生什么?

The .pepk file is only needed when you are already publishing an app and had initially opted out of Play Signing. .pepk文件在您已经发布应用程序并且最初选择退出 Play 签名时才需要。 This is the way to securely transfer your app signing key to Google.这是将您的应用签名密钥安全地传输给 Google 的方法。

If you're creating a new app, you don't need this file, you can enroll in Play Signing immediately selecting the first option "Let Google manage and protect app signing key (Recommended)" and Play will generate the app signing key for you.如果您正在创建一个新应用程序,则不需要此文件,您可以立即注册 Play Signing,选择第一个选项“让 Google 管理和保护应用程序签名密钥(推荐)”,Play 将为您生成应用程序签名密钥你。 If you want to also keep a hold of the private key, you can use the option "Export and upload a key from Java keystore" which will give you the tool and commands to run (unfortunately, the .pepk file cannot be used in this flow the moment).如果您还想保留私钥,您可以使用“从 Java 密钥库导出并上传密钥”选项,这将为您提供要运行的工具和命令(不幸的是, .pepk文件不能在此使用流动的时刻)。

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 我们可以使用现有的密钥库和应用程序签名密钥作为私钥,而使用新的密钥库文件来生成用于 Google Play 应用程序签名的上传密钥吗 - Can we use existing keystore and app signing key for private key whereas new keystore-file for generating an upload key for google play app signing 为什么在新版 Google Play Console 网站中不再使用“private_key.pepk”文件来生成应用签名密钥? - Why isn't "private_key.pepk" file not used to generate app signing key in the new version of Google Play Console website anymore? 统一Google Play应用签名问题和密钥库 - unity google play app signing issue and keystore Google Play应用签名过程 - Google Play App Signing Process 如何启用和编辑pepk.jar文件Google Play应用签名 - How to enable and edit pepk.jar file Google Play App Signing 应用已发布,但我们一直在开发新功能。 我是否应该使用调试或发布密钥库来获取Google Maps Api Key的SHA? - App is published but we keep developing new features. Should I use debug or release keystore to get the SHA for Google Maps Api Key? 丢失应用程序的密钥库文件(但启用了 Google Play 应用程序签名) - Lost keystore file for app (but have Google Play App Signing enabled) Google Play 应用签名证书和上传证书在 Google Play 控制台中创建了相同的 SHA1 密钥 - Both Google Play App Signing Certificate and Upload Certificate created Same SHA1 key in Google Play Console Google Play控制台中的应用签名页面 - App signing page in google play console 使用 Google Play 控制台签署 Flutter 应用程序 - Signing a Flutter App with Google Play Console
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM