Skip to main content

How can we help you today?

Search results for:fastlane

Fastlane export issue
was contributed by @kwoylie, and applies if you have a Gemfile in your repository and you use the fastlane… Gemfile content was: gem "fastlane", "1.104.0" gem "gym", "1.10.0" gem "badge", "0.5.0" gem "CFPropertyList… ","2.3.3" gem "sqlite3", "1.3.11" Fastlane, with xcpretty disabled, produced the following error on
Fastlane Step does not get the FASTLANE SESSION variable correctly
A possible workaround can be to use a Script Step (instead of the Fastlane Step) to launch your Fastlane… The Fastlane Step does not correctly get the FASTLANE_SESSION variable causing two-factor authentication… Apple services connection Fastlane
Installing a specific Fastlane version
For example: gem "fastlane", "2.166.0" The Fastlane Step will install this version before running… /usr/bin/env bashset -exgem uninstall fastlane --all --executables gem install fastlane --version 2.166.0… --no-document Make sure that your Fastlane Step has the Should update fastlane gem before run?
Configuring fastlane match for Bitrise
If you want to use fastlane match in your bitrise.io build, you only have to do three things: Make… If you use match in your Fastfile or fastlane config: match(app_identifier: "my.domain", type: "appstore
Transporter transfer failed, issuer ID is required
When trying to deploy your build via Fastlane (or the Deploy to iTunes Connect with Deliver step, which… uses Fastlane), you encounter the following error: Transporter transfer failed… /fastlane/issues/20741
Found multiple versions of Xcode in /Applications/ error
A build using fastlane can fail with the following error message: Build failed to compile with Xcode… To do so, turn off xcodebuild_formatter in fastlane, or export the logs as a build artifact
Managing a large number of provisioning profiles and certificates
If you have a large number of provisioning profiles and certificates, you can use Fastlane Match Step… Learn how you can configure the Fastlane Match Step… If you don't want to use the Fastlane Match Step, you can find tips on managing the number of profiles
Deploy to App Store fails with "Could not determine the package’s bundle ID. The package is missing an Info.plist or the CFBundlePackageType is not ‘APPL’ or ‘FMWK’ (-21017)
ITMSTRANSPORTER_FORCE_ITMS_PACKAGE_UPLOAD variable in your files, as described here ​ ​https://github.com/fastlane… /fastlane/issues/20371
explicit provisioningProfiles mapping doesn't override Xcode project settings
distribution method is used, even though it seems to be set correctly in Bitrise and in their chosen fastlane