-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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 "increment_build_number" not working after update Fastlane or xcode... #3877
Comments
Hi @mcactive. Thanks for letting us know. Can you edit to include your fast file? Follow the template here: https://github.com/fastlane/fastlane/blob/master/ISSUE_TEMPLATE.md Also, what version of Xcode are you using? Thanks! |
Hi! Yeah, I've stripped the Fastfile to exclude all the errors and even the simplest doesn't work. I've edited the post! Xcode version is the latest, 7.3 |
@mcactive I found a similar issue from a long time ago about a bug with cocapods. Are you using cocapods? Could you check your |
@i2amsam Hi Sam, yes, we are using cocoapods and using the cocoapods action in Fastlane as well. The file appears to be XML instead of the OpenStep format.. Is there an easy way to fix it? |
@mcactive does this solution work? CocoaPods/CocoaPods#613 (comment) it seems like a cocapods issue rather than a fastlane issue. |
@i2amsam you're right... Saving something in xcode and running only But it's weird if it is a cocoapods issue as it always worked and after updating fastlane and xcode it broke... Should I make an issue at CocoaPods? |
@mcactive I agree, super weird. I don't see anything in the fastlane release that seems suspicious, and we didn't run into it with an updated xCode, let's see if anyone else reports it. |
@i2amsam updating to the beta version of cocoapods fixed the issue. This also installs "xcodeproj" beta which fixes a bug in Xcode 7.3:
|
Ran into the same issue. We're using Cocoapods as well, but it isn't part of our fastlane flow. However, I do have a custom action that use the Based on your current finding I would suspect that a change in the xcodeproj structure in Xcode 7.3 has caused an incompatibility with the For now I'm working around the issue by having the |
@vfog I think you are exactly right. I'm seeing the same, and not using cocoapods. |
@mcactive I believe this one should be reopened until its resolved. |
Didn't know fastlane also used Xcodeproj gem. Will reopen it until further notice. |
Look like its defined here. I think this needs to be bumped to minimum |
@mcactive and @kcharwood Thanks! 👍 I put a comment over in #3945, it appears we won't be able to bump our min version because that would put |
@kcharwood I'm closing this issue out so we can track on the other ticket. Thanks for working with us! |
You can put the Fastfile in a subdir => Dir_where_xcodeproj/Fastlane/Fastfile Due other error I have removed increment_build_number, using now a private lane 'update_build_number'
|
Hi!
Just updated both Fastlane and Xcode to the latest version and both increment_build_number and increment_version_number are not working anymore... It doesn't throw an error, it just doesn't update.
The xcode project hasn't been changed at all... The code is pretty straight forward:
increment_build_number build_number: $appJson['version_no'] increment_version_number version_number: $build_number
Complete fastfile:
Output:
Environment
fastlane version (fastlane -v): 1.67.0
xcode version: 7.3
Do you use bundler, rbenv or rvm? RVM
The text was updated successfully, but these errors were encountered: