New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fastlane deliver ignoring increment_version_number for Xcode 13.4.1 #20465
Comments
It seems like you have not included the output of |
I think there's a new option in Xcode that is called "automatic version numbering" or similar. Here Xcode will "hijack" and automatically increase the build/version number by itself. Probably we need to switch to some kind of manual numbering here, which has not been implemented. |
Same-ish problem on Xcode 13.4.1 |
Should manually setting the version in xcode work for now then? So I can still build with 13.4.1 |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
Just adding that problem persists on latest fastlane + Xcode 14.0.1 |
I'm currently setting up fastlane, and I came across this issue as well. The only solution I've found is to use the fastlane-plugin-versioning plugin. In the docs, they mention supporting |
Thanks for this, it would be good to get some clarification on whether this is going to be handled in a future version of fastlane or is something we'll need to accommodate ourselves - I currently manually set the marketing (and any extension) version in Xcode but it feels rubbish :) |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
We started encountering this but with the build number, it always gets set to (1) for some reason. Is there a fix for this? I tried setting Xcode to 13.1 but no success. |
Discussed in #20464
Originally posted by michaelmoneypenny July 13, 2022
For some reason fastlane has started ignoring the dynamic version number we pass in to the pipeline and using the marketing version defined in xcodeproj (9.9.9 in my case)
We haven't changed anything in fastlane around versioning (we have updated Xcode to 13.4.1 and upped the minor version of the app)
What's strange is we can see the correct version at various stages in the pipeline logs but when it gets to deliver it chooses 9.9.9.
Update - reverting to Xcode 13.1 and the correct version is set again - is this a bug or something I need to configure on the build machine for 13.4.1?
Section of fast file (we haven't changed anything here)
Versioning section in Xcode:
Fastlane env:
✅ fastlane environment ✅
Stack
System Locale
fastlane files:
No Fastfile found
No Appfile found
fastlane gems
Loaded fastlane plugins:
No plugins Loaded
Loaded gems
generated on: 2022-07-13
The text was updated successfully, but these errors were encountered: