am ac76a16d: am ae80fd42: am f5aa6752: am 709df4fa: Merge "docs: Fixes for App Indexing training class" into lmp-docs
* commit 'ac76a16d':
docs: Fixes for App Indexing training class
<!-- Accepts URIs that begin with "example://gizmos” -->
<data android:scheme="example"
android:host="gizmos" />
<!-- Accepts URIs that begin with "http://www.example.com/gizmos” -->
<data android:scheme="http"
android:host="www.example.com"
android:pathPrefix="gizmos" />
android:pathPrefix="/gizmos" />
<!-- note that the leading "/" is required for pathPrefix-->
<!-- Accepts URIs that begin with "example://gizmos”
<data android:scheme="example"
android:host="gizmos" />
-->
</intent-filter>
</activity>
</pre>
@@ -76,6 +78,11 @@ in your manifest for deep linking. The URIs {@code “example://gizmos”} and
manifest, Android is able to route any {@link android.content.Intent}
that has matching URIs to your app at runtime.</p>
<p class="note">
<strong>Note:</strong> Intent filters may only contain a single {@code data} element
for a URI pattern. Create separate intent filters to capture additional URI patterns.
</p>
<p>To learn more about defining intent filters, see <a href="{@docRoot}training/basics/intents/filters.html">Allow Other Apps to Start Your Activity</a>.</p>
<h2 id="handling-intents">Read Data from Incoming Intents</h2>
