some more information, another way you can customize your debug application
Id is by following these steps :
1. in your build.gradle
debug {
applicationIdSuffix 'debug'
}
2. in your main manifest file, leave your package declaration but remove it
from all the build-type/flavor specific AndroidManifest files.
this is not generating the issue you mentioned above.
On Thu, Jun 26, 2014 at 5:25 PM, Jerome Dochez <j...@google.com> wrote:
> first, if you are stuck you can always revert to the old manifest merger
>
> android {
> *useOldManifestMerger true*
> }
>
> now, we should not be merging the manifest attributes coming from
> libraries. This is obviously a bug we need to fix on our end.
>
> thanks, jerome
>
>
> On Thu, Jun 26, 2014 at 2:13 PM, Mateusz Grzechociński <
> mateusz.grzechocin...@gmail.com> wrote:
>
>> Hi,
>>
>> after upgrading from gradle android plugin v0.11.1 to latex 0.12,
>> manifest merger raises an exception:
>>
>> :app:processArmMoDebugManifest
>>
>> /Users/mateuszgrzechocinski/dev/myProject/app/src/debug/AndroidManifest.xml:3:11
>> Error:
>>
>> Attribute manifest@package value=(com.myproject) from
>> AndroidManifest.xml:3:11
>>
>> is also present at com.android.support:appcompat-v7:19.1.0:17:11
>> value=(android.support.v7.appcompat)
>>
>> Suggestion: add 'tools:replace="package"' to <manifest> element at
>> AndroidManifest.xml:2:1 to override
>>
>> Mt project has both buildTypes and flavours folders with
>> buildType/fllavor specific resources. In buildType folders I have custom
>> AndroidManifest.xml files which provides some additional activities etc.
>> Above error message is pretty clear. Since I can imagine appcompat
>> library specifies it's own package attribute, there should be an error that
>> gradle plugin accnot assume which package attributes value user want to use.
>>
>> Above error message is clear, so I added:
>>
>>
>>
>> diff --git a/app/src/debug/AndroidManifest.xml
>> b/app/src/debug/AndroidManifest.xml
>>
>> index 71d937a..6df3584 100644
>>
>> --- a/app/src/debug/AndroidManifest.xml
>>
>> +++ b/app/src/debug/AndroidManifest.xml
>>
>> @@ -1,8 +1,11 @@
>>
>> <?xml version="1.0" encoding="utf-8"?>
>>
>> <manifest xmlns:android="http://schemas.android.com/apk/res/android";
>>
>> - package="com.myproject">
>>
>> + xmlns:tools="http://schemas.android.com/tools";
>>
>> + package="com.myproject"
>>
>> + tools:replace="package">
>>
>>
>>
>> - <application>
>>
>> +
>>
>> +<application>
>>
>> Unfortunately, that raises another error, so I'm stuck
>>
>> :app:processArmMoDebugManifest
>>
>> /Users/mateuszgrzechocinski/dev/myProject/app/src/debug/AndroidManifest.xml:2:1
>> Error:
>>
>> tools:replace specified at line:2 for attribute tools:package, but no new
>> value specified
>>
>> /Users/mateuszgrzechocinski/dev/myProject/app/src/debug/AndroidManifest.xml:0:0
>> Error:
>> Validation failed, exiting
>>
>> Any hints, ideas? Because of this possible bug I can't upgrade my Android
>> Studio to beta 0.8 since it requires Gradle plugin version = 0.12.
>>
>> M.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "adt-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to adt-dev+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to adt-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
