ja po tej website instrukcji na temat konfigurowania Fastlane z hockeyapp ale napotkał błądFastlane: Nie wydaje się być kluczowym CURRENT_PROJECT_VERSION ustawić dla tego projektu
:BUILD_NUMBER=>"There does not seem to be a CURRENT_PROJECT_VERSION key set for this project. Add this key to your target's expert build settings."}
Stworzyłem build_number_icon.rb w folderze actions próbowałem nawet skasować numer build_number, a test uruchomić fastlane. Nadal pojawia się ten sam błąd. Czy czegoś brakuje? Czytałem przewodników ponownie, na wypadek, gdy nie zauważyłem schodów.
# 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")
koniec
Wygląda na to, że odpowiedziałeś na własne pytanie, tak jak odpowiadałem! – christopherdrum