IssueTracker

Navigation recently added support for providing intent actions and mimeTypes to nav deep links.

The manifest merger does not currently have the logic needed to consider these fields when generating the intent filters. That logic should be added.

If the custom action in the navigation xml is not an empty string, its value should replace the default android.intent.action.VIEW in the intent filter's <action android:name> element. If the action is an empty string, the <action android:name> element should be removed.

If the navigation xml is provided with a mimeType, its value should be added to the intent filter in an <data android:mimeType> element.

Here are some basic examples:

The deep link is given a custom intent action in the navigation xml:

<deepLink app:action=”android.intent.action.MY_ACTION”/>

It should be converted to the following intent filter:

<intent-filter>
  <action android:name="android.intent.action.MY_ACTION" />
  <category android:name="android.intent.category.DEFAULT" />
  <category android:name="android.intent.category.BROWSABLE" />
</intent-filter>

The deep link is given a mimeType in the navigation xml:

<deepLink app:mimeType=”image/jpg”/>

It should be converted to the following intent filter:

<intent-filter>
  <action android:name="android.intent.action.VIEW" />
  <category android:name="android.intent.category.DEFAULT" />
  <category android:name="android.intent.category.BROWSABLE" />
  <data android:mimeType=”image/jpg” />
</intent-filter>

To see more details and examples, take a look at the design doc.