Pfthb

I am working in Cordova and AndroidStudio to create Android/iOS apps. Everything was working fine until I updated my Cordova to 8 yesterday. I also updated Node to the latest. When I create a Cordova project and add the Android platform. It yields a totally different directory structure. I cannot see assets, res and src folders in project's platform directory D:testApp1platformsandroid. More importantly, the above directory is missing AndroidManifest.xml, which is causing the admob plugin to fail in getting added.

Here is the error that I get while adding the plugin:

Failed to install 'cordova-plugin-admobpro': Error: ENOENT: no such file or directory, open 'D:ProjectstestApp1platformsandroidAndroidManifest.xml'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.readFileSync (fs.js:551:33)
at Object.parseElementtreeSync (D:ProjectstestApp1platformsandroidcordovanode_modulescordova-commonsrcutilxml-helpers.js:180:27)
at new AndroidManifest (D:ProjectstestApp1platformsandroidcordovalibAndroidManifest.js:29:20)
at AndroidProject.getPackageName (D:ProjectstestApp1platformsandroidcordovalibAndroidProject.js:99:12)
at Api.addPlugin (D:ProjectstestApp1platformsandroidcordovaApi.js:223:57)
at handleInstall (C:UsersRaoAppDataRoamingnpmnode_modulescordovanode_modulescordova-libsrcplugmaninstall.js:594:10)
at C:UsersRaoAppDataRoamingnpmnode_modulescordovanode_modulescordova-libsrcplugmaninstall.js:357:28
at _fulfilled (C:UsersRaoAppDataRoamingnpmnode_modulescordovanode_modulescordova-libnode_modulesqq.js:787:54)
at self.promiseDispatch.done (C:UsersRaoAppDataRoamingnpmnode_modulescordovanode_modulescordova-libnode_modulesqq.js:816:30)

Can someone please help?

Final edit:

cordova-android 7.1.2 is out, it should fix most of this kind of problems.

edit:

As people keep upvoting the answer I'll give more details about the problem.

The problem isn't really the plugin writing on the AndroidManifest.xml or on the config.xml. It's true that the location changed and plugins should update the path, but it's not mandatory and Cordova takes care of the new paths.

The problem is some plugins using source-file tag for things that are not source code. (i.e, using it for copying images instead of using resource-file tags)
That creates a res folder (or lib) that confuses Cordova, making it believe it's an old Eclipse project, while it's really an Android studio project, and searches for the files on the old locations instead of looking into the new locations.

This has been patched in cordova-android and will be fixed in next release.
The workaround is to look for the plugin using source-file tag and update it to use resource-file tag

OLD ANSWER:

It is now in app/src/main/AndroidManifest.xml.

If the plugin is writing on it, it should be updated to write on the right place.

Read the cordova-android 7.0.0 release blog post

Cordova CLI v8.0 will use cordova-android@7.0.0 by default.

As most of the cordova plugins do not support cordova-android@7.0.0 yet, you can also try using the older one by specifying version:

cordova platform add android@6.4.0

Or, if you feel comfortable to use cordova-android@7.0.0, you can also wait for a update on cordova-plugi-admobpro to support the cordova-android@7.0.0, it's coming soon.

In config.xml file of the cordova project, under xml tag <platform name="android"> section, Add the following tag:

<resource-file src="platforms/android/app/src/main/AndroidManifest.xml" target="AndroidManifest.xml" />

I simply fixed the error by copying AndroidManifest.xml
in

platformsandroidappsrcmain

to

platformsandroid

1. Firstly make sure the plugin supports cordova android 7.0.0+


2. Delete all of these folder or file: ['AndroidManifest.xml', 'libs', 'res'] in the platforms/android root directory.

Cordova use these files to determine if your project is an eclipse project. If they are existed, your project will be treated as an eclipse project with the old path structure. Some plugin may create these files/folders on your android folder.

The problem appears to be when you try to build for release at the same time you are running the App locally. I stop the App on localhost and then build for release. Problem solved.