Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 52857 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Our current AndroidManifest.xml merging process seems to be a bit limited. There are many use-cases where advanced manifest merging rules are needed to accomplish certain tasks within application development.
Gradle build currently supports quite an extensive AndroidManifest.xml merging process. You can see details outlined here:
These are mainly accomplished with merge rule markers defined by the xmlns:tools="http://schemas.android.com/tools".
Sample inside a <manifest>:
Within these tools, there are different markers that apply a rule. Here are a couple of examples:
tools:node="merge" - Merges all attributes in this tag and all nested elements given there are no conflicts
tools:node="merge-only-attributes" - Merge all attributes in this tag only, do not merge nested elements
tools:node="remove" - Remove the element from the merged manifest
tools:node="removeAll" - Remove all elements matching the type
tools:node="replace" - Replace the lower priority element
tools:node="strict" - Creates a build failure when the element in lower priority doesn't match the high priority manifest rule
There is also a concept of Attribute Markers in which you can apply merge rules to specific attributes.
For example I could apply one of rules without the "node" definition to an attribute instead:
Thus would remove the "android:windowSoftInputMode" attribute.
All of these features would be extremely useful for MSBuild and Xamarin.Android. It would allow application developers to customize their build process when dealing with third party SDKs and complex manifest merging that might add unwanted nodes/attributes to their application. This is common in native Android app development that involve advanced manifest merging tactics.
Whether this is supported in XML or via the Xamarin.Android flavored Attributes, it would cause less grief on our customers who try to integrate with third party libraries and need to customize the manifest merging process.
Related Issue: https://bugzilla.xamarin.com/show_bug.cgi?id=48153
Related Issue: https://bugzilla.xamarin.com/show_bug.cgi?id=51689
*** Bug 48153 has been marked as a duplicate of this bug. ***
Adding a +1; I maintain a nuget at my company that's used for a number of internal projects. It would benefit from features to allow its users to override some of its permissions requests.
+1 - my team needs this as well
added a feature request on github as per Jon for this
+1 - this is critical for us as we try to move from GCM to Firebase Messaging.