---
# System prepended metadata

title: 'GoCD Fastlane iOS version number, filters - Wed 30th Sept, 2020'
tags: [C+, filters, CFBundleVersion, buildnumber, infoplist, gocd, iOS, programmingjournal, '2020', testflight, fastlane]

---

# GoCD Fastlane iOS version number, filters - Wed 30th Sept, 2020

I had a *fun* pipeline issue yesterday. In order to push a new app version to the iOS App Store, you must increment the app's build number (`CFBundleVersion`). I was doing this, but the app was continually being rejected, saying a build with that number had already been submitted.

Long story short: I inadvertently had added the [increment_build_number](https://docs.fastlane.tools/actions/increment_build_number/) Fastlane action, which seemed to override whatever higher version I had in my info.plist and thus cause my problem.

In the future I think I will use [the latest testflight build number](https://docs.fastlane.tools/actions/latest_testflight_build_number/) as my source of truth, which should both prevent this problem and mean I don't have to manually up the version.

This was useful to debug the build number problem in the pipeline:

```bash=
grep CFBundleVersion ios/connectplus/Info.plist -A1 
```

I also continued to work on filters in C+. Will try and finish tomorrow.

###### tags: `programmingjournal` `2020` `C+` `filters` `gocd` `iOS` `buildnumber` `infoplist` `testflight` `fastlane` `CFBundleVersion`