Remove backup to prevent manifest merger conflicts #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
commonsguy
added a commit
that referenced
this pull request
Jun 22, 2014
Remove backup to prevent manifest merger conflicts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not exactly sure if there was a reason for the "allowBackup" in the libraries manifest, but it seems to be the cause of a Gradle import issue. I don't know what version of Gradle this became an issue in, but it is present on my project using Gradle 0.11+ and Android Studio 0.6.1.
The error thrown is a manifest merge error. This change puts the manifest more in line with the SackList manifest
Currently, the solution to get around this is to set
useOldManifestMerger truein your gradle build properties.