Android-manifest file

android-manifest File One manifest function
Global configuration file for the application
Portal Configuration for Applications
Unique specified name of the package
Android Four components definition: Activity,service, broadcast Receiver Content Provider
Define the new application
Define instrumentation to do automated testing
Define the minimum SDK required for your application
List the class libraries required by the application


II. structure and definition
Some of the commonly used tags:
<manifest>
The definition of four components:<application>
Permissions used by the application:<uses-permission/>
Custom Permissions:<permission/>
Custom permission tree-Convenient when we have a lot of permissions when:<permission-tree/>
Custom Permission Group:<permission-group/>
Test component (unit test mainly):<instrumentation/>
Version of the SDK used:<uses-sdk/>
</manifest>


Conventions of the three documents
Elemental element:
All lowercase
<manifest><application> must have and have only one
The order of elements of the same level is independent, such as the order of activity at the same level can be different, but <activity-alias> must follow <activity>
Property Attitude:
Processing the Name property is optional
In addition to the properties of the <manifest> package= "Chengzhi.hello", the rest is preceded by Android:


The analytic way of four manifest
1 when the application is installed, the manifest information is placed in a system's index table
2 When the system starts, Packagemanageserviceduqu manifest information
3 When the application starts, launcher makes system-level judgments, such as the smallest SDK, etc.
44 large components are instantiated when needed, and only one main activity is activated when the system is first started

Android-manifest file