There was a recent SWAT ticket where this step worked differently than the customers bash script. Upon further investigation I think the step was configured differently that the bash script and that caused the version numbers not being updated.
I have included some extra logs to help debug future issues.
Changes
There is a new verbose input which will make the step print more useful logs for debugging. The new debug logs will look like this:
Updating build settings for the Example target
CURRENT_PROJECT_VERSION 1 -> 9999
MARKETING_VERSION 1.0 -> 9.99.9
Checklist
step.ymlandREADME.mdis updated with the changes (if needed)Version
Requires a PATCH version update
Context
There was a recent SWAT ticket where this step worked differently than the customers bash script. Upon further investigation I think the step was configured differently that the bash script and that caused the version numbers not being updated.
I have included some extra logs to help debug future issues.
Changes
There is a new verbose input which will make the step print more useful logs for debugging. The new debug logs will look like this:
and
So it will print out which target or info.plist path is being updated and also it will print the old values too.