Replies: 2 comments 4 replies
-
The issues you mentioned above is not incorrect mechanism. You can commit to the
The new pushed commit won't be executed by the CircleCI. You can ignore committing the build_number as well. But when you merge it back to |
Beta Was this translation helpful? Give feedback.
-
Just wanted to put this here but... 2FA shouldn't be a problem in the near-ish future. All of the APIs that use I should maybe get some information out on how to initially start testing / using that 🤔 |
Beta Was this translation helpful? Give feedback.
-
Just wondering what the best way of going about this would be, considering the fact that due to 2FA restrictions it's impossible to get the build number from Appstore Connect.
I did this:
to create a new build, merge the code from
develop
instaging
. In CircleCI I have a job that only runs on staging that executes my fastlanebetaRelease
lane.That all works fine but the main issue is the build number. I wanted to simply get the latest build number from Appstore Connect, increase it and use it, but because of 2FA issues (check Github issues for that) this is not a stable option.
So next I tried: increase the build number in the project file, build, push the increased build number to github. This however also has issues as:
staging
has changed, and we effectively get into an infinite loop.Is there another way to manage the build number somehow? I don't care that it's not in the project file. As long as it's always incremented while building it's fine.
Beta Was this translation helpful? Give feedback.
All reactions