Manifest merger failed: Attribute
provider#com.google.firebase.provider.FirebaseInitProvider#authorities value=(fintnessathome.cardioexcercise.firebaseinitprovider) from AndroidManifest.xml:766:13-86
is also present at [com.google.firebase:firebase-common:19.3.0] AndroidManifest.xml:28:13-72 value=(com.fintnessathome.fintnessathomeapp.firebaseinitprovider).
Suggestion: add 'tools:replace="android:authorities"' to <provider> element at AndroidManifest.xml:764:9-768:39 to override.
I am facing this issue, I got the template from my friend and i want to make some changes in the android app, it's showing this error when I execute this program.
Try adding following Code in your manifest.xml
tools:replace="android:allowBackup"
Try adding the following in the gradle.properties file
android.useAndroidX=true
android.enableJetifier=true
android.enableUnitTestBinaryResources=false
Also, add the following code into your manifest file inside the application tag
tools:replace="android:supportsRtl,android:allowBackup,icon,label"
Related
When adding <application android:testonly="True"> to my AndroidManifest.template, I get : E2312 ..\Android\Debug\Project1\AndroidManifest.xml:34: error: No resource identifier found for attribute 'testonly' in package 'android'. It's the same for release.
Is there a way to get an apk with this attribute with delphi ?
You cannot place it in Manifest.
Instead you must add android.injected.testOnly=false in your "gradle.properties" file
Error:Execution failed for task ':app:processDebugManifest'.
Manifest merger failed : Attribute meta-data#android.support.VERSION#value value=(26.0.0-beta1) from [com.android.support:appcompat-v7:26.0.0-beta1] AndroidManifest.xml:28:13-41
is also present at [com.android.support:support-v4:26.1.0] AndroidManifest.xml:28:13-35 value=(26.1.0).
Suggestion: add 'tools:replace="android:value"' to element at AndroidManifest.xml:26:9-28:44 to override.
Try to fix the version mentioned in your gradle file.
All of the dependencies should have same version number.
Answer is already provided in ur error...
just goto ur manifest, inside application tag put this : tools:replace="android:value"
Edit version com.android.support:appcompat:26.1.0 and com.android.support:support:26.1.0 same.
Add this line into manifest:
<application
...
...
tools:replace="android:value">
I have an android app and i've defined android:supportsRtl="false" (Without it - it was rtl and I don't want it).
Now i'm using this library:
compile 'com.iceteck.silicompressorr:silicompressor:2.0'
And the my code doesn't compile:
Error:Execution failed for task ':app:processDebugManifest'.
Manifest merger failed : Attribute application#supportsRtl value=(false) from AndroidManifest.xml:40:9-36
is also present at [com.iceteck.silicompressorr:silicompressor:2.0] AndroidManifest.xml:17:9-35 value=(true).
Suggestion: add 'tools:replace="android:supportsRtl"' to element at AndroidManifest.xml:36:5-189:19 to override.
I'm not completely understanding how should I implement the suggestion, or if there is another way to solve it.
I've tried tools:replace="android:supportsRtl=false" but it still doesn't compile
Thanks!
Ideally, you would use true for supportsRtl. And, ideally, the library would not be setting any value for supportsRtl.
However, the instructions in the error message should be straightforward:
Suggestion: add 'tools:replace="android:supportsRtl"' to element at AndroidManifest.xml:36:5-189:19 to override
Since we don't have your manifest, we have to guess as to what is on those lines. Most likely, you should add tools:replace="android:supportsRtl" to your <application> element, in addition to your android:supportsRtl="false" that you already have there.
I am integrating payumoney in my android application. I have read docs and see video for integration i.e < https://www.youtube.com/watch?v=gnQ0IF3XniM&t=740s >. Problem is when i am trying to import module dependency it gives me error that manifest merger failed with multiple error.
C:\Users\amit\Desktop\New folder (3)\SalwarTales-master\app\src\main\AndroidManifest.xml:22:9-38 Error:
Attribute application#icon value=(#drawable/logo) from AndroidManifest.xml:22:9-38
is also present at [:sdkui] AndroidManifest.xml:20:9-43 value=(#mipmap/ic_launcher).
Suggestion: add 'tools:replace="android:icon"' to <application> element at AndroidManifest.xml:20:5-72:19 to override.
C:\Users\amit\Desktop\New folder (3)\SalwarTales-master\app\src\main\AndroidManifest.xml:26:9-43 Error:
Attribute application#theme value=(#style/NoActionBar) from AndroidManifest.xml:26:9-43
is also present at [:sdkui] AndroidManifest.xml:22:9-40 value=(#style/AppTheme).
Suggestion: add 'tools:replace="android:theme"' to <application> element at AndroidManifest.xml:20:5-72:19 to override.
finally did it. very silly mistake. I was using Different launcher icon and app theme in both modules.
I am trying to dexguard an application that I run as a system application.
However when I try to push it to the system/app directory, I get the following error from the PackageParser.
W/PackageParser( 1995): /system/app/My.apk (at Binary XML file line #290): <a
ctivity> does not have valid android:name
I have also added the following to the dexguard-project.txt but to no avail.
-keepresourcexmlattributenames
manifest/installLocation,
manifest/versionCode,
manifest/package,
manifest/versionName,
manifest/application/*/intent-filter/*/name,
manifest/application/*/activity/name
Does anyone know how to solve this issue?
UPDATE
Ok from what I see the manifest/application/*/activity/name successfully stopped the android:name attributes from being obfuscated in the manifest (I can see the plain text when I extract the manifest file after the obfuscation).
However strangely enough android:name in the activity tag at line #290 cannot be found in the extracted manifest file. All the other activity names can be seen in plain text.
In my case the package name of the class started with a Capital letter
I found out that this is because the activities that gave this error are in the manifest file but there were no respective java classes.
Removing the entries from manifest file solved the issue.