dpa99c
commented
7 years ago In isolation, the operation to remove that element works fine:
console output
``` $ more config.xmlHowever, while the plugin can remove config elements using <preference delete="true" /> syntax, it can't prevent other plugins adding it, which is what's happening in your case:
You are including cordova-plugin-x-socialsharing in your project which adds the WRITE_EXTERNAL_STORAGE permission in its plugin.xml.
Due to the way the Cordova CLI lifecycle works, if a plugin listed in the config.xml is missing from the plugins/ folder (e.g. in a CI environment where they are installed fresh every time), Cordova will install those plugins after any after_prepare hook scripts have finished execution (i.e. this plugin). Therefore, this plugin is actually removing the element, but the social sharing plugin is re-adding it again:
console output
``` $ more config.xmlHowever, once the plugin is present in the local project, subsequent prepare operations will not re-invoke its installation and therefore not re-add its config:
console output
``` $ cordova plugin ls cordova-custom-config 3.0.14 "cordova-custom-config" cordova-plugin-whitelist 1.0.0 "Whitelist" cordova-plugin-x-socialsharing 5.1.6 "SocialSharing" $ more config.xmlIf you really need to remove this permission (I'm not sure why this would be essential) and you are unable to build in a local environment where the locally installed plugins persist, you could fork the social sharing plugin in order to remove that preference from its plugin.xml to prevent it being added to the AndroidManifest.xml each time the plugin is installed.
JarLowrey
Adding the preference
among others, does not have any effect. When building, the AndroidManifest is regenerated and the permissions re-appear. I have tried deleting all platforms and plugins, re-adding the android platform and running
cordova prepareto re-download the plugins.You can see my entire config.xml here. Thanks!