Develop Reference

Package is not specified in the manifest file

While trying to create and Extract string from the layout file it is showing the alert dialog that Package is not specified in the manifest file. It is happening from while I had updated my studio to the newest version(chimpunk 2021.2.1) and the newest gradle(7.2). any help will be appretiated.

I had the same problem. Open AndroidManifest.xml and add your package name back.
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
package="YOUR_PACKAGE_NAME"> <!--This is what I added-->

React Native: Error: Package name not found

After integrating RN into an existing Android project, I get the following error:
Error: Package name not found in /home/.../AndroidManifest.xml at Object.projectConfig (/home/.../rn_integrated_app/node_modules/#react-native-community/cli-platform-android/build/config/index.js:74:11) at Object.get project [as project]
As I understand the problem is that there is no package attribute in the relevant AndroidManifest.xml file. Since my project has many flavors, the package attribute is added dynamically, while compiling, through app/build.gradle:
def pkgDataEntry = getRightValue(packagesData, variantMap)
variant.getMergedFlavor().applicationId = pkgDataEntry.pkg
So that the final merged manifest file does have the package attribute.
The error occurs here(#react-native-community/cli-platform-android/build/config/index.js):
const packageName = userConfig.packageName || getPackageName(manifest);
if (!packageName) {
throw new Error(`Package name not found in ${manifestPath}`);
}
Is there a way to make RN read the merged manifest file?
If not, how can I modify userConfig to contain the package name? I couldn`t find anything about it in the docs.
Thank you

For me, the solution was to add the "package" tag to the manifest tag.
I didn't have to create another dummy folder.
The manifest open tag now looks like this:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.yourProjectName">

If anybody encounters the same issue, when having multiple flavors and AndroidManifest.xml files,here`s my conclusion:
RN has some kind of a bug that it requires the first folder alphabetically, in android/app/src, which has AndroidManifest.xml file,to have the package attribute. Otherwise, it will throw an error.
A simple solution would be to create a dummy folder, e.g aaa (first alphabetically) and to create AndroidManifest.xml inside of it, with the following attribute - package:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="aaa"
xmlns:tools="http://schemas.android.com/tools">
<uses-permission
android:name="android.permission.GET_ACCOUNTS"
tools:node="remove"/>
</manifest>

For me, this error start after upgrade the sdkVersion from 31 to 33 and gradle version.
I did check the changes in git, and notice that the package attribute was removed from AndroidManifest.xml.
So I did add this attribute again.
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.yourpackage">

Android Studio using a library and project with the same package name

I have a library I use as a base for all my android apps and has the following manifest file:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.android"
xmlns:tools="http://schemas.android.com/tools"
android:versionCode="36"
android:versionName="1.b" >
<uses-sdk
android:minSdkVersion="5"
android:targetSdkVersion="21"
tools:overrideLibrary="com.facebook.android"/>
I then try to use it in one of my projects which has the following manifest:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.android"
xmlns:tools="http://schemas.android.com/tools"
android:versionCode="36"
android:versionName="1.6" >
<uses-library
android:name="com.example.android"
android:required="true"/>
<uses-sdk
android:minSdkVersion="5"
android:targetSdkVersion="21"
tools:overrideLibrary="com.facebook.android"/>
Note that the package name used is the same: com.example.android. Since the app is published under com.example.android, I cannot change it for the app. As for the library, for historical reasons, it has the same pacakge name. When I build the project, I get the following error:
FAILURE: Build failed with an exception.
What went wrong: Execution failed for task ':exampleCom:processDebugResources'.
Error: A library uses the same package as this project: com.example.android You can temporarily disable this error with
android.enforceUniquePackageName=false However, this is temporary and
will be enforced in 1.0
I do not want to change the package name of either library or app. I am not sure where to add the "android.enforceUniquePackageName=false" . Any ideas? Also, how to solve beyond 1.0 (which I am already using)?

You can add enforceUniquePackageName=false in the app modules build.gradle file under android:
android {
compileSdkVersion 23
buildToolsVersion "23.0.1"
enforceUniquePackageName = false
...
}
Unfortunately this results in another problem with an unfixed bug from the build tools.
Error:Execution failed for task
':app:packageAllDebugClassesForMultiDex'.
java.util.zip.ZipException: duplicate entry: ... BuildConfig.class
See https://stackoverflow.com/a/27310034/668400

An ounce of prevention is worth a pound of cure. It may not help this particular situation, but for future developers to avoid getting into this situation, please note the JLS recommendation in Chapter 6. Names which addresses this very problem:
Package Names
Developers should take steps to avoid the possibility of two published
packages having the same name by choosing unique package names for
packages that are widely distributed. This allows packages to be
easily and automatically installed and catalogued. This section
specifies a suggested convention for generating such unique package
names. Implementations of the Java SE platform are encouraged to
provide automatic support for converting a set of packages from local
and casual package names to the unique name format described here.
If unique package names are not used, then package name conflicts may
arise far from the point of creation of either of the conflicting
packages. This may create a situation that is difficult or impossible
for the user or programmer to resolve. The class ClassLoader can be
used to isolate packages with the same name from each other in those
cases where the packages will have constrained interactions, but not
in a way that is transparent to a naïve program.
You form a unique package name by first having (or belonging to an
organization that has) an Internet domain name, such as oracle.com.
You then reverse this name, component by component, to obtain, in this
example, com.oracle, and use this as a prefix for your package names,
using a convention developed within your organization to further
administer package names. Such a convention might specify that certain
package name components be division, department, project, machine, or
login names.

Package name is a unique identifier for a package and therefore you should not have the same package name for both the library and the application. Change the package name for the library if the application is already published.

worked on as 2.2, gradle 2.14.1
android {
enforceUniquePackageName = false
//it was deprecated, but still work
android.packageBuildConfig = false
...
}
details:new-build-system

Get applications package name

I am using Xamarin. I need to get the Google Maps API key and to do this I need my application's package name. How do I get this?
My app is called SimpleMapDemo and is one of the samples for using Google Maps.

Open your Manifest file and you shall find the package name of your application from the <manifest> tag.
Below is an example:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.recorder"
android:versionCode="1"
android:versionName="1.0" >
In the above example my applications package name is: com.example.recorder

Overwrite Android Application

I'd like to overwrite my old android application. What are the things i have to be do for that ?
Do Changes in AndroidManifest.xml is enough ?
I like to use another package structure and a new project to do so.
Regards.

Following are required:
Same key
Same Package Name
Higher versionCode in the manifest

The package name indicated in the manifest should be the same:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.company.demo.app"
android:versionCode="1"
android:versionName="1.0" >

If you're talking about the registration in Google Play, I think that only the package="..." attribute of the <manifest> node must be the same (and the version must be superior to the one of your first application of course).
It must also be signed with the same key.
That way, the Google Play site will recognize your old application as a new version, and it will replace the old one.