Plugin breaking Android and iOS version codes about cordova-custom-config

[dpa99c]

Short answer - add this to your config.xml:

<preference name="cordova-custom-config-autorestore" value="false" />

Long answer: this is being caused as a side effect of the backup behaviour which is turned on by default in the plugin (I may have to reconsider this). The plugin attempts to make custom config settings "removable" by taking a backup of the platform config files before the first prepare operation after the plugin is installed. In theory this should restore the original platform config file, allowing this plugin and cordova to modify it to produce an up-to-date version. Without this behaviour, if a custom config setting defined in the config.xml is applied to a platform config file, then removed from the config.xml, there's no (easy) way to remove the corresponding config setting from the platform config file. The backup script is invoked as a before_prepare hook, but it seems that cordova updates the version numbers in the platform config files even before the before_plugin hook scripts are executed, hence any updates made by cordova to version numbers are being overwritten when the backup platform config file is restored. Unfortunately there's not a before_before_prepare hook to restore the backups before cordova updates the version numbers, so for now the simple solution, as I've said above, is to turn off the auto-restore of backup files. Of course, this will have the side effect that any custom config values you remove from your config.xml will not be removed from the corresponding platform files, so you'll need to do this manually.

[bostondv]

Awesome, that did the trick.

For my case I'm totally satisfied without the backup behaviour and I think
it may make sense to default it to off. Although it's handy, it's easy
enough to remove manually a value one time from the platform file.

Thanks!

On Tue, Feb 2, 2016 at 4:30 PM Dave Alden [email protected] wrote:

Short answer - add this to your config.xml:

Long answer: this is being caused as a side effect of the backup behaviour
https://github.com/dpa99c/cordova-custom-config#backups which is turned
on by default in the plugin (I may have to reconsider this). The plugin
attempts to make custom config settings "removable" by taking a backup of
the platform config files before the first prepare operation after the
plugin is installed. In theory this should restore the original platform
config file, allowing this plugin and cordova to modify it to produce an
up-to-date version. Without this behaviour, if a custom config setting
defined in the config.xml is applied to a platform config file, then
removed from the config.xml, there's no (easy) way to remove the
corresponding config setting from the platform config file. The backup
script is invoked as a before_prepare hook
https://github.com/dpa99c/cordova-custom-config/blob/master/plugin.xml#L22,
but it seems that cordova up dates th e version numbers in the platform
config files even before the before_plugin hook scripts are executed,
hence any updates made by cordova to version numbers are being overwritten
when the backup platform config file is restored. Unfortunately there's not
a before_before_prepare hook to restore the backups before cordova
updates the version numbers, so for now the simple solution, as I've said
above, is to turn off the auto-restore of backup files. Of course, this
will have the side effect that any custom config values you remove from
your config.xml will not be removed from the corresponding platform
files, so you'll need to do this manually.

—
Reply to this email directly or view it on GitHub
#25 (comment)
.