Geek Answers Handbook

Fastlane: It seems that the CURRENT_PROJECT_VERSION key is not set for this project

I have been following this website for setting up fastlane with hockeyapp, but I ran into an error

:BUILD_NUMBER=>"There does not seem to be a CURRENT_PROJECT_VERSION key set for this project. Add this key to your target expert build settings."}

I created the build_number_icon.rb file in the action folder, and even tried to make hardcode build_number and test runlane. Still getting the same error. Am I missing something? I read the guides again if I skipped steps.

  # Build and publish the Beta version to Hockeyapp lane :beta_hockeyapp do # Build build_app( # Not a production release, so add build number and do the color modulation of the icons release:false, # Modulate the colors of the icons by these degrees modulation:66.6, # Change the app name app_name:"<App Name>", # Set the app id app_identifier:"com.company.<appname>", # Set the path to the certificate to use in building certificate_path:"./Certificates/Company/<cert>.p12", # Set the password of the p12 certificate file certificate_password:"<password>", # Set the path to the provisioning profile to use (change this!) profile:"./Certificates/Company/<profile>.mobileprovision", # What configuration to use, usefull for keeping different API keys etc between environments configuration:"[INT] <project_name>", # Use this codesigning identity (this is the name of the certificate in your keychain) codesigning_identity:"Project Distribution", # Export an enterprise app export_method:"enterprise", # the projectname, this is the name of the .xcodeproj file and the folder containing your code in the project project_name:<Project>, # the scheme to build scheme:"Project-Internal", # the build number to use, we use the build number from Jenkins build_number: "1234" || ENV["BUILD_NUMBER"] ) # Push to Hockeyapp as Beta release publish_hockey(release_type: "0")

end

+6
source share
2 answers

Fixed a bug where you had to set the number in the project build settings> Current project version.

+10
source

I use fastlane, but not with hockey. I personally have not come across this problem. However, a warning alerts you to a specific problem in your target tool target> build setting (specified in the "Current version of the project" section in the "Versions" section). Enter CURRENT_PROJECT_VERSION in the search field and you will see that this is a different value than your build_number. My project is not set up, but I think hockey may have different needs?

In any case, it seems that you do not notice the exact meaning of the key value.

+8
source

More articles:


All Articles