Skip to content
This repository has been archived by the owner on Mar 6, 2024. It is now read-only.

Getting ManifestMerger2 MergeFailureException on basic project #16

Open
DarioAhdoot opened this issue Dec 1, 2017 · 3 comments
Open
Labels

Comments

@DarioAhdoot
Copy link

As mentioned in the other Issue, I'm having Manifest Merging issues, even on Android Gradle Plugin 2.2.3 and with build cache disabled.

I've attached a minimum reproducible example:
FatAarExample.zip

Here we have three Library projects (LibraryA, LibraryB, and LibraryC), and a fourth (FatLibrary) which tries to embed them.

Import this into Android Studio. Both Syncing and Building will fail with the given exception.

Please let me know if you have any questions.

@vigidroid
Copy link
Owner

To add this line to the manifest node in your main manifest file does the trick.

xmlns:tools="http://schemas.android.com/tools"

I will try to fix it someday.

@vigidroid vigidroid added the bug label Dec 4, 2017
@DarioAhdoot
Copy link
Author

Thanks, that fixed the minimum reproducible example I provided, but we're still seeing the issue with our actual project. I'll have to do some more investigating. Our manifests are basically identical, as are our build.gradle files. Frustrating.

@vigidroid
Copy link
Owner

@Diarrhio yes it's frustrating. In the source code of android plugin, the handling of manifest merge part is such complicated.
You can post the full stacktrace of your project, to try the luck.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants