Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Instant App - Digital Asset Links Protocol

Whenever I tried to upload my instant app apks to Play store, it gives the following error :

  • Your site 'www.mywebsitename.com' has not been linked through the Digital Assets Link protocol to your app. Please link your site through the Digital Assets Link protocol to your app.

However, whenever I execute https://developers.google.com/digital-asset-links/tools/generator, it gives success for associating with my app and web site. Any idea why am I getting this error? What may cause this?

Thanks for help in advance.

like image 450
senaaltun Avatar asked Jun 23 '17 14:06

senaaltun


People also ask

What is Digital Asset link?

Overview. The Digital Asset Links protocol and API enable an app or website to make public, verifiable statements about other apps or websites. For example, a website can declare that it is associated with a specific Android app, or it can declare that it wants to share user credentials with another website.

Where should I put json Assetlinks?

In order for Android to automatically create the link between your website and your app, you need to host a file on your website. This file, assetlinks. json, must be located at https://yoursite.com/.well-known/assetlinks.json (if you're using a subdomain, be sure to specify https://yoursubdomain.yoursite.com/…)

What is well known Assetlinks json?

/.well-known/assetlinks.json (spec) A Google specification that allows a site to define its relationship to apps or other sites, e.g. allow links to a site to be opened in an app instead.


2 Answers

Please check whether Google Play App Signing is enable on Google Play Console. If Google Play App Signing is enable, Google Play Console will replace your app key with release key. And the key you set on Android Studio is treated as upload key. So, you need to modify your assetlinks.json with release key.

like image 101
user3813078 Avatar answered Sep 22 '22 05:09

user3813078


This happened to me when I had generated an assetlinks.json file from my debug keys, rather than the release keys. It shows up as verified in Android Studio, then fails on the server. 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. 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. 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"). 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.

like image 38
Troy Avatar answered Sep 22 '22 05:09

Troy