• Android development in the androidmanifest. XML configuration root node <manifest> configuration details
  • Android manifest.xml configuration <application> configuration details
  • The <manifest> subtag configuration of androidmanifest.xml in Android development
  • Android manifest.xml configuration <activity> tag configuration details
  • Android manifest.xml configuration <activity-alias> tag configuration details
  • Androidmanifest.xml configuration for implicit Intent tags
  • Android development in the Androidmanifest. XML configuration of service, receiver tag configuration details

This article focuses on sharing the tag configuration associated with implicit intEnts. If there are any mistakes, please correct them. More Android technology sharing can pay attention to my Android technology circle, you can also join QQ group number :690347536, learn to exchange Android development skills.



1. android:icon

Icon identification.

2. Android :label Label.

Android :priority Execution priority. A larger value indicates a higher priority. The value ranges from -1000 to 1000.

4. Android :order Indicates the filtering order.



1. android:name

The action name.



1. android:name

The category name.



1. android:scheme

The URI scheme

2. Android :host HOST of the URI

3. Android :port Indicates the port of the URI

Android: Path 5. Android :pathPrefix 6. Android :pathPattern 4, 5, and 6 indicate path rules in the URI.

7. Android :mimeType MINE multimedia type.

The preceding tags are intended to be used in the Intent’s implicit matching. The general matching rules are as follows: 1. The action,category, and data in the filter list must be matched at the same time. 2. An Intent can have multiple actions, categories, and data categories that form different categories. An Intent must match both the action category and the data category to be a complete match. 3. An Activity, Service, and BroadcastReceiver can contain multiple groups of intent-filters. If an intent matches any group of intent-filters, it is considered a successful match.

The matching rules of the action are as follows: 1. The name attribute of the action is strictly case-sensitive. 2. The Intent must contain an action, but not a category. 3. A matching rule can have multiple actions at the same time, but the action in an Intent needs to be the same as one of them to be successfully matched.

Matching rules for category: 1. Although you can not add a category in the Intent, but in starting the Activity, Service component or send the radio, the system will automatically add a “android. The Intent. The category. The DEFAULT” DEFAULT category. 2. Multiple categories can be set in an Intent at the same time. Once multiple categories are set, each category must be able to match one of the categories specified in the filtering criteria.

Data description and matching rules: 1. In JS call native components, data is very useful; 2. If an intent-filter defines data, the Intent must define a matching data. 3. Data is made up of two parts: mineType and URI. 4. 5. URI structure: < scheme > : / / < host > : < port > / / < path > | < pathPrefix > | < pathPatten >], path, pathPattern can represent the complete path information, The pathPattern can contain wildcard character *, indicating zero or more arbitrary characters. PathPrefix indicates only the pathPrefix.

Follow for more Android technology sharingMy Android tech circle, you can also join QQ group number :690347536 to learn and exchange Android development skills.