You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the main docs page, the following 2 lanes are defined:
lane:betadoincrement_build_numberbuild_appupload_to_testflightendlane:releasedocapture_screenshotsbuild_appupload_to_app_store# Upload the screenshots and the binary to iTunesslack# Let your team-mates know the new version is liveend
Is there a reason the release lane isn't including increment_build_number?
If a dev currently uses the following workflow:
Deploys beta
Tests
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.
The text was updated successfully, but these errors were encountered:
GioLogist
changed the title
Fastlane, main docs
Fastlane, main doc beta & release lanes
May 2, 2019
In the main docs page, the following 2 lanes are defined:
Is there a reason the release lane isn't including
increment_build_number
?If a dev currently uses the following workflow:
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.The text was updated successfully, but these errors were encountered: