简体繁体 English

即时应用程序 - 数字资产链接协议

[英]Instant App - Digital Asset Links Protocol

原文 2017-06-23 14:22:36 4 4 android/ android-instant-apps/ digital-assets-links

Whenever I tried to upload my instant app apks to Play store, it gives the following error : 每当我尝试将我的即时应用apks上传到Play商店时，都会出现以下错误：

Your site 'www.mywebsitename.com' has not been linked through the Digital Assets Link protocol to your app. 您的网站“www.mywebsitename.com”尚未通过数字资产链接协议链接到您的应用。 Please link your site through the Digital Assets Link protocol to your app. 请通过Digital Assets Link协议将您的网站链接到您的应用。

However, whenever I execute https://developers.google.com/digital-asset-links/tools/generator , it gives success for associating with my app and web site. 但是，每当我执行https://developers.google.com/digital-asset-links/tools/generator时，它都会成功与我的应用和网站相关联。 Any idea why am I getting this error? 知道为什么我会收到这个错误吗？ What may cause this? 可能是什么原因导致的

Thanks for help in advance. 提前感谢您的帮助。

4 个解决方案

Please check whether Google Play App Signing is enable on Google Play Console. 请检查Google Play控制台是否启用了Google Play App Signing。 If Google Play App Signing is enable, Google Play Console will replace your app key with release key. 如果启用了Google Play App Signing，Google Play控制台将使用发布密钥替换您的应用密钥。 And the key you set on Android Studio is treated as upload key. 您在Android Studio上设置的密钥被视为上传密钥。 So, you need to modify your assetlinks.json with release key. 因此，您需要使用发布密钥修改assetlinks.json 。

This happened to me when I had generated an assetlinks.json file from my debug keys, rather than the release keys. 当我从调试密钥生成assetlinks.json文件而不是发布密钥时，这发生在我身上。 It shows up as verified in Android Studio, then fails on the server. 它在Android Studio中显示为已验证，然后在服务器上失败。 Double check that the signing config is correct for your asset links file, and that the fingerprint in the file matches the SHA256 fingerprint of your release key. 仔细检查签名配置对于资产链接文件是否正确，以及文件中的指纹是否与释放密钥的SHA256指纹匹配。 You can get your release key's fingerprint by running 您可以通过运行获取释放密钥的指纹

keytool -list -v -keystore ~/my_keystore.jks

Another cause can be if you've enabled Play signing. 另一个原因可能是您启用了Play签名。 In that case, you have to use the fingerprint provided in your developer console, not the one for the key you signed the APK with locally (the local one is called your "upload key"). 在这种情况下，您必须使用开发人员控制台中提供的指纹，而不是您在本地签署APK的密钥（本地一个称为“上传密钥”）。 This isn't obvious in Android Studio at all, since its asset link file generator doesn't give you an option to put in a custom fingerprint. 这在Android Studio中根本不明显，因为它的资产链接文件生成器不会为您提供放入自定义指纹的选项。

Please check if your website asset link file is not behind some form of authentication, internal IP, or blocked by firewall. 请检查您的网站资产链接文件是否不在某种形式的身份验证，内部IP或防火墙阻止之后。 Play Store Developer Console can not access the digital asset link file if it is not publicly accessible. Play Store Developer Console如果无法公开访问，则无法访问该数字资产链接文件。

That said, please double check if https://www.mywebsitename.com/.well-known/assetlinks.json is accessible from external network (switch to a public wifi and verify the json file can load properly). 也就是说，请仔细检查是否可以从外部网络访问https://www.mywebsitename.com/.well-known/assetlinks.json （切换到公共wifi并验证json文件是否可以正确加载）。

As Jarrod said in a comment, if all else fails then discard the staged release and re-upload the APK. 正如Jarrod在评论中所说的那样，如果其他所有方法都失败了，那么就放弃分阶段发布并重新上传APK。 Just now worked for me. 刚刚为我工作。