


Note: Default values for each attribute are documented in the Manifest reference. Therefore, the value of each attribute should be explicitly defined as per requirement.

Hence, it is applied to the merged manifest file. For an instance, if the higher priority manifest uses “standard” as the default value for the android:launchMode attribute, without declaring it in the file and the lower-priority manifest assigns a different value to the same attribute, that value overrides the default value. Therefore, it is advisable not to be dependent on the default attribute values. As all the unique elements are combined into the same element, a Merge Conflict may occur. Sometimes, it is possible that the higher-priority manifest is dependent on the default value of an attribute, but this value is not declared in the file.

