The package name of the manifest file in the library project and the app project are not the same

There is a package name in the manifest file , as follows ：

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" xmlns:tools="http://schemas.android.com/tools" package="a.b.c">

	...

</manifest>

This package name is used for IDE The package name of the generated resource file , such as ：

a.b.c.R.id
a.b.c.R.string
a.b.c.R.layout
a.b.c.BuildConfig

stay BuildConfig There is a property in ：DEBUG, Can be used to judge the current App yes Debug Version or Release edition , If the package name in a library project manifest file and app The package name in the project manifest file is the same , It's in App Runtime , Access to the a.b.c.BuildConfig Is generated in the library project , If the library project is using release Version of , It's in App Accessed in BuildConfig.DEBUG The attribute is ture, And we are App In the project , This attribute is used to determine App yes Debug Version or Release edition , Instead of trying to determine what version the library project is , therefore , To prevent this , To combine library items with App The package name in the manifest file of the project is set to different .