Fastlane, main doc beta & release lanes

[GioLogist]

In the main docs page, the following 2 lanes are defined:

lane :beta do
  increment_build_number
  build_app
  upload_to_testflight
end

lane :release do
  capture_screenshots
  build_app
  upload_to_app_store       # Upload the screenshots and the binary to iTunes
  slack                     # Let your team-mates know the new version is live
end

Is there a reason the release lane isn't including increment_build_number?

If a dev currently uses the following workflow:

1. Deploys beta
2. Tests
3. Deploys release

With the current script, they'll run into an issue where there is already an existing app with the same build # & version #. I suggest we add increment_build_number to the release lane, so as not to confuse devs into thinking that its handled automagically via release lanes somehow.

[janpio]

I think that is a valid point. Or are there common scenarios where this would not be needed? Does this maybe assume the user does this manually?

I guess it is this way to not overcomplicate things, but if this results in broken uploads for users this of course doesn't help.

[GioLogist]

Yea, exactly. It'll definitely result in broken uploads.

With the workflow, we have two options:

1. Log into App Store connect and submit the same build currently on TestFlight
2. Use fastlane, but with an incremented build number.