Correctly update the properties for all build configurations #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes issue #12
The problem is that getBuildProperty without the last parameter returns only the value of one of the many available build configurations.
Now, what happens if the value returned by getBuildProperty has the expected value, but the other build configurations still have the wrong value? Simple: the plugin (wrongly) assumes that the value does not need to be changed, so it does not update its value, which results in a Cordova project that works in one build configuration, but is totally broken when changing build configuration.
This patch fixes the problem by iterating through each build configuration, and updating the values accordingly.