General issues

While building an Android app, you receive the error: java.lang.ClassNotFoundException.

You may be receiving this error because of a mismatch between your app's Java version and the Java Virtual Machine's (JVM) version. You can update your Java version by adding the Set Java Version Step to your Workflow and setting the Java version to be set globally for the build input variable.

If you perform a simulator reset during the build, for example with a pre-action Build Phase Script xcrun simctl erase all, it can cause Xcode or the simulator to hang.

Remove the simulator reset script and rebuild.

I cannot see my GitHub Organization/repository on the Add New App page.

You probably did not grant access to bitrise.io when you authenticated with GitHub to access the Organization (or a repository owned by the Organization).

To fix this you should follow this guide: Grant access to a GitHub Organization.

How can I grant Bitrise access to a Bitbucket team?

This guide explains how to grant access for bitrise.io to your Bitbucket team.

How can I generate an SSH key pair?

If you want to do manual SSH key configuration on bitrise.io, you can generate an appropriate SSH keypair with a simple Command Line / Terminal command:

ssh-keygen -t rsa -b 4096 -P '' -f ./bitrise-ssh -m PEM

This will generate two files in the current directory (the directory where you run the command):

You should copy paste the public key to your Git hosting service (for example, GitHub, Bitbucket), and when you register your app on bitrise.io, you’ll have to provide the private key.

How can I grant access for bitrise.io to my GitHub Organization?

You have to grant access through the Settings options of your GitHub avatar.

You can see the Organization and its repositories if you go back to bitrise.io, click on your avatar, select Add new App and hit Next.

You'd like to have a build create a new branch in your Github repository.

You can use a Script Step to make an API call to your Github repository. You can use this to create a new branch, as described in this thread: https://stackoverflow.com/questions/9506181/github-api-create-branch

How can I add projects with submodules or with private repo dependencies?

You try to use a script or tool which requires permissions where OS X presents a popup for acceptance (for example an osascript).

You can use a workaround to allow the tool, without manual interaction by the user. For example, try using https://github.com/jacobsalmela/tccutil.

To add osascript to the allowed OS X Accessibility list, you can call tccutil from your script (don’t forget to include it in your repository or download on-the-fly): sudo python tccutil.py -i /usr/bin/osascript

You can download the script from GitHub directly. For example: wget https://raw.githubusercontent.com/jacobsalmela/tccutil/master/tccutil.py.

You get the following error when running your build on Bitrise:

_ld: file not found ..._

Perform the following steps and after each step check if it has solved your problem:

If none of the above helped, try deleting the Xcode local cache. After that the error should be reproducible on your local machine.

You can delete the local Xcode cache using your Terminal:

rm -rf ~/Library/Developer/Xcode/DerivedData

Your build trigger does not trigger a build automatically on Bitrise.

Workflow Editor doesn't load for you.

If Workflow Editor doesn’t load, chances are your bitrise.yml or a Workflow which you have configured crashes the Workflow Editor’s UI.

If you face the above issue please first:

If I enable the Bitrise Support user what can it do and can't do?

First, you need to sign in with your Github account, or sign up if you don’t have one yet.

Let’s see the tools you need to install and use Middleman.

Middleman is distributed using the RubyGems package manager. This means you need both the Ruby language runtime installed and RubyGems to begin using Middleman.

MacOS comes prepackaged with Ruby, however, some of Middleman’s dependencies need to be compiled during installation. On macOS that requires Xcode which you can install via the Mac App Store. Alternatively, you can just install the Xcode Command Line Tools, that should be enough if you don’t want to install the full Xcode app.

Once you have Ruby and Xcode (Command Line Tools), execute the following from the command line:

gem install middleman

This will install Middleman, its dependencies and the command-line tools.

Now that you have installed Middleman, let’s create a new Middleman project!

Before you start, make sure you’re signed up to Bitrise either via your git provider or email.

The above code installs the dependencies specified in your Gemfile, and runs a Middleman build on the virtual machine.

Now we are going to add and customize an Amazon S3 bucket sync to the workflow steps.

Alternative deploy targets

You can of course use Heroku, GitHub pages or any other service as your deployment target.

Once the configuration of your Workflow is complete, you can run a build manually by clicking on the Start/Schedule a build button on the app’s page.

If you chose GitHub when adding your repository, each code change (commit) on GitHub will automatically trigger a Bitrise build. Otherwise you can find more information about how you can setup a Webhook, to trigger builds automatically for code push, pull request and tags here.

If you have your resources on your server in a zip archive, it’s very simple to download it:

The source code of your app will be (by default) downloaded into the folder defined in the $BITRISE_SOURCE_DIR Env Var.

You can also place the content of your ZIP archive into a specific folder within your app’s source code directory. Just define the destination folder of the ZIP resource archive downloader Step like this: ${BITRISE_SOURCE_DIR}/folder_name or .folder_name.

If you only want to download a single file, use the File Downloader Step.

If you want to control the whole download process, you can use the Script Step and write your own download code. For example:

#!/bin/bashset-ex# Download your resource
curl -fo"download/path""https://url/of/your/resource"# Uncompress it
unzip -u"download/path"-d"uncompress/target/path"

If you’d need an additional tool to download or uncompress the resources file, please read our Install Any Additional Tool_ guide.

Every time a Step fails, the entire build fails as well. However, certain Steps aren't crucial to the build so they should be considered skippable.

The easiest way is to add the is_skippable option to the Step or Steps in question and set it to true.

To do this, you need to go to yml mode. You can either:

- Go to the bitrise.yml tab on the Workflow Editor and edit the Step there.

- Download the bitrise.yml file, edit it in your editor of choice and upload it again.

In the bitrise.yml file, find the Workflow you need and within the Workflow, the Step you want to mark as skippable. Add is_skippable: true to it. Here's an example of a Script Step:

- script:
    is_skippable: true
    inputs:
    - content: |-
        #!/bin/bash
        echo "Failing Step."
        exit 1
        # exit 1 would mark this step as Failed, but it won't break the Build
        #  because of the is_skippable: true flag / property

Enabling or disabling a Step conditionally

How to grant access for bitrise.io to your GitHub Organization.

The iOS Auto Provision with Apple ID Step fails with the following error:

Identify Certificates on Developer Portal

development certificate: Development is not downloadable, skipping...

development certificate: Development is not downloadable, skipping...

Development certificates on Apple Developer Portal:

production certificate: Distribution is not downloadable, skipping...

Production certificates on Apple Developer Portal:

searching for Certificate: Apple Development: xxxxxxx (YYYYYYYY) [aaaaaaaaaaaaaaaaaaa]

Error:
no development nor production certificate identified on development portal

The account used needs to have the ADMIN role on the Apple Developer account.

You can't build with Android NDK as the Android Build Step constantly fails with the following error:

Execution failed for task ':app:extractSmartMessagesReleaseNativeSymbolTables'.
> NDK is not installed

You even tried adding the Install missing Android SDK components Step to your Workflow, but the error persists.

We recommend that you check which NDK version you need for your project (based on the Android plugin you use), and include it in the build with a Script Step. Use sdkmanager in the Script Step to install the NDK:

sdkmanager "ndk;VERSIONNUMBER"

Your build fails with the following error message:

 /Users/vagrant/Library/Developer/Xcode/DerivedData/nwReactNativeApp-hjmnjyfndsswkmfhbbryzhnwpgvh/Build/Intermediates.noindex/ArchiveIntermediates/nwReactNativeApp-qa/BuildProductsPath/QA-iphoneos/XCFrameworkIntermediates/ChatProvidersSDK/ChatProvidersSDK.framework/Modules/ChatProvidersSDK.swiftmodule/arm64-apple-ios.swiftinterface:217:49: use of unknown directive '#filePath'

This type of project only supports Xcode 12.0 and above. Therefore, we recommend that you update the stack to 12.0+ on the Stack tab of Bitrise and run a new build.

You are building a swift CLI app, which means the main target cannot have tests directly associated.

The workaround described here is to define a second target and scheme to only use for testing. The Xcode Test for Mac Step, however, breaks on this type of scheme because it attempts to run the "build" action, which causes this error:

 "The scheme 'MyTestScheme' is not configured for running."

Make sure that the Run action is checked for the test scheme, as the error message suggests. You could also try to run the main scheme instead of the test scheme, since for that the Run action is checked by default.

The latest version of a community created Step does not show up in the Workflow Editor. The new version is available in the Step's repository but it can't be selected in the Workflow Editor.

Creating a new GitHub release in the Step's repository is only part of the whole release process.

The Step creator has to notify Bitrise that there is a new Step version available. To do so, the Step's creator has to open a new PR to the Step within the Bitrise Step Library.

In general, the above process might take some time, but if you think the Step creator has not opened a PR to Bitrise, you can also ask the Step creator if the pull request has already been made. If all goes well, you'll have the new version available soon in your Workflow Editor!

Your build fails due to the following error:

FATA[21:32:35] [ENVMAN] environment list too large

You have to increase the available Env Var list size. You can easily do so manually if you add the following into a Script Step:

#!/usr/bin/env bash
# fail if any commands fails
set -e
# debug log
set -x

mkdir -p ~/.envman && echo -e '{"env_list_bytes_limit_in_kb": 200}' > ~/.envman/configs.json