[英]Will opting in for Google Play App signing for AAB upload affect existing users who have already installed APK from playstore?
As everyone is aware now Google has made it compulsory to upload AABs instead of APKs.众所周知,谷歌现在强制要求上传 AAB 而不是 APK。 I have an app in play store that has a huge user base who have installed the older version and we haven't opted for Google Play App Signing from the beginning and now as we are forced to upload the AABs and upload AABs we have to opt-in Google Play App Signing .
我在 Play 商店中有一个应用程序,该应用程序拥有庞大的用户群,他们安装了旧版本,我们从一开始就没有选择Google Play 应用程序签名,现在我们被迫上传 AAB 并上传 AAB,我们不得不选择- 在Google Play 应用程序签名中。 As per my understanding, Google will sign its own certificate on top of my certificate.
据我了解,谷歌将在我的证书之上签署自己的证书。 So I have the following questions for the community to clarify
所以我有以下问题需要社区澄清
Right now we can't test it on other apps as there is no option to upload APKs.目前我们无法在其他应用上测试它,因为没有上传 APK 的选项。
Opting in on Play Signing does not affect your users.选择加入 Play Signing 不会影响您的用户。 When you enroll an existing app, you effectively have to upload your private key to Google so that they can do the signing on your behalf, so end users will still receive APKs signed with the same key, and thus won't have to reinstall the app.
当您注册一个现有的应用程序时,您实际上必须将您的私钥上传到 Google,以便他们可以代表您进行签名,因此最终用户仍会收到使用相同密钥签名的 APK,因此不必重新安装应用程序。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.