Hi all,
In following up on #5, I can confirm that setting the version information in the iOS PList-file seems to work fine. However, I would like more control over the format of the version strings stored in the CFBundleVersion and CFBundleShortVersionString properties. For, up to this point we've been setting CFBundleVersion to the build ID (the sequential build number) and CFBundleShortVersionString to major.minor. However, your task sets both the the full four-number version string, whereas judging from other implementations I've seen, this does not seem to be unusual. Hence, unless we would switch to using custom regular expressions again, we won't be able to use your VSO-task to version our PList-files... As such, I'd like to request a change 😄
Best regards,
Alexander.
Hi all,
In following up on #5, I can confirm that setting the version information in the iOS PList-file seems to work fine. However, I would like more control over the format of the version strings stored in the
CFBundleVersionandCFBundleShortVersionStringproperties. For, up to this point we've been settingCFBundleVersionto the build ID (the sequential build number) andCFBundleShortVersionStringto major.minor. However, your task sets both the the full four-number version string, whereas judging from other implementations I've seen, this does not seem to be unusual. Hence, unless we would switch to using custom regular expressions again, we won't be able to use your VSO-task to version our PList-files... As such, I'd like to request a change 😄Best regards,
Alexander.