简体   繁体   English

使用Google Play应用签名将同一应用签名证书与其他应用一起使用

[英]Use the same App-Signature-Certificate with different apps using Google Play App Signing

I have two different apps, and I want them to be able to communicate together. 我有两个不同的应用程序,希望它们能够相互通信。 For security reasons, I would like to restrict the communication with protectionLevel:signature, so I don't have to worry about other apps possibly messing with my apps. 出于安全原因,我想使用protectionLevel:signature限制通信,因此我不必担心其他应用程序可能会干扰我的应用程序。

The problem is, I use Google Play Signing for the first app. 问题是,我在第一个应用程序中使用了Google Play签名。 I noticed, that when I want to create a new App in the play console, and opt-in for Google Play App Signing, that another certificate is generated. 我注意到,当我想在播放控制台中创建一个新的应用程序并选择加入Google Play应用程序签名时,会生成另一个证书。 So, I suspect that the permission system is not working, as the release-apk that users download will not be signed by the same certificate, and that the "protectionLevel=signature" check will fail. 因此,我怀疑权限系统无法正常工作,因为用户下载的release-apk不会由同一证书签名,并且“ protectionLevel = signature”检查将失败。

Is this true, or will it still work somehow when the Upload-Certificate matches? 这是真的,还是当“上传证书”匹配时仍然可以正常工作吗? Is there any way to use the same certifiacte for different apps using Google Play App Signing? 是否可以通过Google Play App签名对不同的应用使用相同的证书?

I solved it; 我解决了; There is a button for reusing the Signing Key from an old app in the "App Signature" Tab in the play console. 在播放控制台的“应用程序签名”标签中,有一个用于从旧版应用程序重新使用签名密钥的按钮。

Note that after you generated a distribution key once, it cannot be changed, even if you never uploaded an APK yet, so you have to press the button to reuse the key immediately before generating another distribution key. 请注意,一次生成分发密钥后,即使您从未上传过APK,也无法更改,因此您必须在生成另一个分发密钥之前立即按按钮重新使用密钥。

I had to delete my (unpublished) app and created a new one. 我必须删除(未发布的)应用程序并创建一个新的应用程序。 If you already published you app (even if just for a closed beta test), your only chance to get the same distribution key is to create a new app with a different app id. 如果您已经发布了应用程序(即使仅用于封闭Beta测试),则获得相同分发密钥的唯一机会是使用其他应用程序ID创建一个新应用程序。

暂无
暂无

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

相关问题 Google Play App签名和签名级别权​​限 - Google Play App Signing and signature level permission Google Play 应用签名证书和上传证书在 Google Play 控制台中创建了相同的 SHA1 密钥 - Both Google Play App Signing Certificate and Upload Certificate created Same SHA1 key in Google Play Console Android Google Play应用程序使用多个应用程序签名 - Android Google Play App Signing with Multiple Apps Google Play应用签名和即时应用 - Google Play App Signing and Instant Apps 使用现有的使用普通签名的android应用程序,即使我使用Google Play应用程序签名来更改符号,为什么也要对其进行更新? - With existing android apps that use ordinary signing, why can I update it even if I change the sign using Google Play App Signing? Google应用签名会更改我的应用证书吗? - Does Google app signing change my apps certificate? 如何配置build.gradle以使用Google Play App签名上传证书 - How to configure build.gradle to use Google Play App Signing upload certificate 如何将一个帐户用于多个应用程序(AccountAuthenticator、sharedUserId、Google Play App Signing)? - How to use one account with multiple apps (AccountAuthenticator, sharedUserId, Google Play App Signing)? 使用自签名证书签署应用程序是否会影响哪些 Android 设备可以在 Play 商店中看到该应用程序? - Does using a self-signed certificate for signing apps influence which Android devices can see the app in the Play Store? 关于Google Play App签名 - About Google Play App Signing
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM