Full control of the AndroidManifest.xml [$20]

[vidplace7]

Allow for full control over the contents of the AndroidManifest.xml.

This is crucial to allow developers to limit devices that can install their APKs, for instance, apps that require BLE using the tag.

Perhaps allow for custom XML to be passed to the build script, or add new fields for each XML tag.

Did you help close this issue? Go claim the $20 bounty on Bountysource.

[knappador]

You can overwrite templates/AndroidManifest.tmpl.xml on your own. There is also a manifest extras option inside that template near the bottom. If you want a buildozer option to make it easier to overwrite the template in its entirety, you would need to file the bug on buildozer. I'm pretty sure there should already be options for including the manifest extras.

[tito]

Yes, but no.

Having an option or something to control the xml is necessary. If you want to automate the build, you don't want to overwrite templates, specially if the templates change in the python-for-android itself.

We just need to find a solution for it :) (maybe xpath based or something)

[mraygalaxy]

+1 - we definitely need more control. =)

[vidplace7]

Can we please re-open this ;) It hasn't really been addressed yet

[kamathln]

+1 for re-opening

We can definitely pass along the manifest as a element tree or something. Recipes and such can play around with the element tree adding and modifying nodes.

[daytipper1989]

You can overwrite templates/AndroidManifest.tmpl.xml on your own. There is also a manifest extras option inside that template near the bottom. If you want a buildozer option to make it easier to overwrite the template in its entirety, you would need to file the bug on buildozer. I'm pretty sure there should already be options for including the manifest extras.

When I overwrite the AndroidManifest.tmpl.xml, it is regenerated everytime I deploy and my changes are lost. Why is this happening with me? any idea? please help.