Lines Matching refs:json

146   the app’s intent filters against the Digital Asset Links files ({@code assetlinks.json}) hosted
190   filters would fail verification if an {@code assetlinks.json} file were not found at both
191   {@code https://www.domain1.com/.well-known/assetlinks.json} and
192   {@code https://www.domain2.com/.well-known/assetlinks.json}:
225   hosts, you must host a separate {@code assetlink.json} file on each subdomain. For example, an
227   owner published valid {@code assetlinks.json} files at both
228   {@code https://www.example.com/.well-known/assetlinks.json} and
229   {@code https://mobile.example.com/.well-known/assetlinks.json}:
252   file, with the name {@code assetlinks.json}, at the following well-known location on the domain:
256 https://<em>domain</em>[:<em>optional_port</em>]/.well-known/assetlinks.json
286   The following example {@code assetlinks.json} file grants link-opening rights to a
306   A website can declare associations with multiple apps within the same {@code assetlinks.json}
309   <code>https://www.example.com/.well-known/assetlinks.json</code>:
349   assetlinks.json} files. The following file listings show an example of how to declare the
355 https://www.domain1.com/.well-known/assetlinks.json
372 https://www.domain2.com/.well-known/assetlinks.json