I don't know about that sort of manifest merging, but if you use the UsesPermission attribute in C# in the library, the permissions should be added to the manifest of the consuming project. Convention is to put them in AssemblyInfo.cs but as it's an assembly-level attribute you can put them in any .cs file.
[assembly: UsesPermission(Android.Manifest.Permission.Internet)] [assembly: UsesPermission(Android.Manifest.Permission.Vibrate)] [assembly: UsesPermission(Android.Manifest.Permission.WriteExternalStorage)] [assembly: UsesPermission(Android.Manifest.Permission.ReadExternalStorage)] [assembly: UsesPermission(Android.Manifest.Permission.AccessCoarseLocation)] [assembly: UsesPermission(Android.Manifest.Permission.AccessFineLocation)]
I'm not aware of any issues coming from using the attribute in my 6 years of Xamarin experience.
I merge all the time. Not everything is supported, but that is how permissions, activities, etc all work.
I describe it in my video: https://www.youtube.com/watch?v=7kVeC1_14Ag
You can find the final merged one in your obj/bin output
i need to subscribe all your youtube updates. i missed that video :D thanks for sharing
Sign in to comment