Understanding Google Advanced Protection and App Installation

Google Advanced Protection Program provides enhanced security features for users who need extra account protection. Recent updates to this program have introduced stricter controls over app installation on Android devices.

What's Changed?

The latest Android security updates with Google Advanced Protection now restrict app installations to recognized app stores only. This is a deliberate security measure implemented by Google to protect high-risk users from potential security threats.

Impact on TestApp.io Users

If you have Google Advanced Protection enabled on your device, you may experience limitations when trying to install apps through TestApp.io. This is because:

• Google Advanced Protection now requires apps to be installed through recognized stores
• This security feature cannot be disabled on protected devices
• The restriction affects all development and testing platforms, not just TestApp.io

TestApp.io's Role

As a development-focused platform, TestApp.io is designed specifically for:

• Facilitating app testing within development teams
• Enabling efficient feedback collection during development
• Supporting the app development workflow

We intentionally maintain our position as a development and testing platform rather than an app store, as this allows us to focus on providing the best possible experience for app testing and team collaboration.

What This Means for Teams

If your organization uses Google Advanced Protection:

• These installation restrictions are part of Google's security framework
• The limitations are a security feature, not a platform issue
• We recommend discussing these limitations with your security team to establish appropriate development testing protocols

Moving Forward

We understand this situation may present challenges for some users. While we cannot override Google's security measures, we remain committed to providing excellent development and testing tools within the bounds of these security protocols.

For any questions about how this affects your specific development workflow, please reach out to our support team.

Additional Resources

• Google Advanced Protection Program Overview
• Android Security Updates

Setup Expo (EAS) with Github Actions to upload your Android (APK) and iOS (IPA) to TestApp.io for testing and feedback.

The following environment variables need to be set:

• TESTAPPIO_API_TOKEN
• TESTAPPIO_APP_ID

iOS

name: Upload IPA to TestApp.io
on:
  workflow_dispatch:

jobs:
  ios:
    runs-on: macos-latest
    steps:
      - name: 🏗 Setup repo
        uses: actions/checkout@v3

      - name: 🏗 Setup Node
        uses: actions/setup-node@v3
        with:
          node-version: 18.x
          cache: yarn

      - name: 🏗 Setup EAS
        uses: expo/expo-github-action@v8
        with:
          eas-version: latest
          token: ${{ secrets.EXPO_TOKEN }}

      - name: 📦 Install dependencies
        run: yarn install

      - name: 🚀 Build app
        run: eas build -p ios --profile staging --local --non-interactive --clear-cache --output "./ipa/ios-staging-build.ipa"
        env:
          SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}

      - name: 🌐 Upload IPA to TestApp.io
        uses: testappio/github-action@v5
        with:
          api_token: ${{ secrets.TESTAPPIO_API_TOKEN }}
          app_id: ${{ secrets.TESTAPPIO_APP_ID }}
          file: ./ipa/ios-staging-build.ipa
          release_notes: ''
          git_release_notes: true
          include_git_commit_id: true
          notify: true

Android

name: Upload APK to TestApp.io
on:
  workflow_dispatch:

jobs:
  android:
    runs-on: ubuntu-latest
    steps:
      - name: 🏗 Setup repo
        uses: actions/checkout@v3

      - name: 🏗 Setup Node
        uses: actions/setup-node@v3
        with:
          node-version: 18.x
          cache: yarn

      - name: 🏗 Setup EAS
        uses: expo/expo-github-action@v8
        with:
          eas-version: latest
          token: ${{ secrets.EXPO_TOKEN }}

      - name: 📦 Install dependencies
        run: yarn install

      - name: 🚀 Build app
        run: eas build -p android --profile staging --local --non-interactive --clear-cache --output "./apk/android-staging-build.apk"
        env:
          SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}

      - name: 🌐 Upload APK to TestApp.io
        uses: testappio/github-action@v5
        with:
          api_token: ${{secrets.TESTAPPIO_API_TOKEN}}
          app_id: ${{secrets.TESTAPPIO_APP_ID}}
          file: ./apk/android-staging-build.apk
          release_notes: ""
          git_release_notes: true
          include_git_commit_id: true
          notify: true

Feedback & Support

Developers built TestApp.io to solve the pain of app distribution for mobile app development teams.

Join our community for feedback and support.

Happy releasing 🎉

Setup Expo (EAS) with Circle CI to upload your Android (APK) and iOS (IPA) to TestApp.io for testing and feedback.

Connect Expo EAS with CircleCI

In order to automatically trigger the CircleCI pipeline, we need to connect our CircleCI project to our repository.

When creating a new CircleCI project, you will have the option to connect a specific repository to the CircleCI project. After the two are linked, we just need to create the environment variables for the CircleCI project.

For more information about creating a CircleCI project, see this.

Environment variables

In order to know where to upload the EAS build, you need to provide the environment variables in the Circle CI project. See this guide for how to add environment variables.

The following environment variables need to be set:

• TESTAPPIO_API_TOKEN
• TESTAPPIO_APP_ID

Filters

In the example configuration, if you look at the workflows in the config, we have a filter to only start the pipeline when the staging branch is changing. If you need to listen for code changes in other branches, just change this value to match your own branch name.

iOS

In this example, we are using the Expo EAS build tool to locally build the app on a CircleCI macOS virtual machine.

EAS is using Fastlane under the hood and is automatically preparing the credentials and signing the build for you. For more information about the local EAS iOS build process, refer to the expo docs.

Create config.yml

version: 2.1

orbs:
  node: circleci/[email protected]

jobs:
  eas_ios_staging_build:
    macos:
      xcode: '15.0.0'
    steps:
      - checkout
      - run:
          name: Install Cocoapods
          command: gem install cocoapods
      - node/install-packages:
          pkg-manager: yarn
      - run:
          name: iOS build
          command: npx eas-cli build -p ios --profile staging --local --non-interactive --clear-cache --output "./ipa/ios-staging-build.ipa"

      - run:
          name: Upload to TestApp.io
          command: |
            export INSTALL_DIR=/tmp
            curl -Ls https://github.com/testappio/cli/releases/latest/download/install | bash
            $INSTALL_DIR/ta-cli publish --api_token=$TESTAPPIO_API_TOKEN --app_id=$TESTAPPIO_APP_ID --release="ios" --ipa=./ipa/ios-staging-build.ipa --notify=true --git_release_notes=true --git_commit_id=true --source="Circle CI"

workflows:
  ios_staging_build:
    jobs:
      - eas_ios_staging_build:
          filters:
            branches:
              only: staging

Android

In this example, we are using the Expo EAS build tool to locally build the app in a Docker container on CircleCI.

EAS is using Fastlane under the hood and is automatically preparing the credentials and signing the build for you. For more information about the local EAS Android build process, refer to the expo docs.

version: 2.1

orbs:
  node: circleci/[email protected]
  android: circleci/[email protected]

jobs:
  eas_android_staging_build:
    resource_class: large
    docker:
      - image: cimg/android:2022.08-node

    steps:
      - checkout
      - node/install-packages:
          pkg-manager: yarn
      - run:
          name: Android build
          command: npx eas-cli build -p android --profile staging --local --non-interactive --clear-cache --output "./apk/android-staging-build.apk"

      - run:
          name: Upload to TestApp.io
          command: |
            export INSTALL_DIR=/tmp
            curl -Ls https://github.com/testappio/cli/releases/latest/download/install | bash
            $INSTALL_DIR/ta-cli publish --api_token=$TESTAPPIO_API_TOKEN --app_id=$TESTAPPIO_APP_ID --release="android" --apk=./apk/android-staging-build.apk --notify=true --git_release_notes=true --git_commit_id=true --source="Circle CI"

workflows:
  eas_android_staging_build:
    jobs:
      - eas_android_staging_build:
          filters:
            branches:
              only: staging

Feedback & Support

Developers built TestApp.io to solve the pain of app distribution for mobile app development teams.

Join our community for feedback and support.

Happy releasing 🎉

Publish your Android & iOS apps from Codemagic to TestApp.io and notify your testers for testing and feedback.

iOS

TestApp.io environment variables in Codemagic

TESTAPPIO_APP_ID
TESTAPPIO_API_TOKEN

These values can be found in App -> Integrations -> Releases

Using Fastlane (Build & Upload)

If you haven't yet, you would need to setup the fastlane and add the TestApp.io plugin.

fastlane add_plugin testappio

Fastlane environment and other configuration can be found in Codemagic documentation: https://docs.codemagic.io/integrations/fastlane-integration/

Create or update: codemagic.yaml file under your project root folder.

workflows:
  ios-workflow:
    name: iOS Workflow
    instance_type: mac_mini_m1 # Specify the instance type, example: mac_mini_m1

    environment:
      xcode: latest # Specify Xcode version, example: 13.3
      groups:
        - default # Example group, add your API tokens here TESTAPPIO_API_TOKEN and TESTAPPIO_APP_ID

    # BUILD AND UPLOAD PHASE
    scripts: 
      - name: Build and upload to TestApp.io
        script: |
          bundle install
          bundle exec fastlane ios development --verbose

Without Fastlane (Upload only)

Create or update: codemagic.yaml file under your project root folder.

workflows:
  ios-workflow:
    name: iOS Workflow
    instance_type: mac_mini_m1 # Specify the instance type, example: mac_mini_m1

    environment:
      xcode: latest # Specify Xcode version, example: 13.3
      groups:
        - default # Example group, add your API tokens here TESTAPPIO_API_TOKEN and TESTAPPIO_APP_ID

    # OUTPUT
    artifacts:
      - build/ios/ipa/app.ipa # This path needs to align with the path in the publish command

    scripts:

      # BUILD
      # Add your build commands here
      #...

      # UPLOAD
      - name: Upload to TestApp.io
        script: |
          #!/bin/bash

          # Download and install the TestApp.io CLI
          curl -Ls https://github.com/testappio/cli/releases/latest/download/install | bash

          # Use the TestApp.io CLI to publish the app
          ta-cli publish \
            --api_token=$TESTAPPIO_API_TOKEN \
            --app_id=$TESTAPPIO_APP_ID \
            --release="ios" \
            --ipa=./build/ios/ipa/app.ipa \
            --notify=true \
            --git_release_notes=true \
            --git_commit_id=true \
            --source="Codemagic"

Android

TestApp.io environment variables in Codemagic

TESTAPPIO_APP_ID
TESTAPPIO_API_TOKEN

These values can be found in App -> Integrations -> Releases

Using Fastlane (Build & Upload)

If you haven't yet, you would need to setup the fastlane and add the TestApp.io plugin.

fastlane add_plugin testappio

Fastlane environment and other configuration can be found in Codemagic documentation: https://docs.codemagic.io/integrations/fastlane-integration/

Create or update: codemagic.yaml file under your project root folder.

workflows:
  android-workflow:
    name: Android Workflow
    instance_type: mac_mini_m1 # Specify the instance type, example: mac_mini_m1

    environment:
      groups:
        - default # Example group, add your API tokens here TESTAPPIO_API_TOKEN and TESTAPPIO_APP_ID
    
    # BUILD AND UPLOAD PHASE
    scripts: 
      - name: Build and upload to TestApp.io
        script: |
          bundle install
          bundle exec fastlane android beta --verbose

Without Fastlane (Upload only)

Create or update: codemagic.yaml file under your project root folder.

workflows:
  android-workflow:
    name: Android Workflow
    instance_type: mac_mini_m1 # Specify the instance type, example: mac_mini_m1

    environment:
      groups:
        - default # Example group, add your API tokens here TESTAPPIO_API_TOKEN and TESTAPPIO_APP_ID

    scripts:

      # BUILD
      - name: Build Android debug
        script: | 
          ./gradlew assembleDebug

       # UPLOAD
      - name: Upload to TestApp.io
        script: |
          #!/bin/bash

          # Download and install the TestApp.io CLI
          curl -Ls https://github.com/testappio/cli/releases/latest/download/install | bash

          # Use the TestApp.io CLI to publish the app
          ta-cli publish \
            --api_token=$TESTAPPIO_API_TOKEN \
            --app_id=$TESTAPPIO_APP_ID \
            --release="android" \
            --apk=./app/build/outputs/apk/debug/app-debug.apk \
            --notify=true \
            --git_release_notes=true \
            --git_commit_id=true \
            --source="Codemagic"

Feedback & Support

Developers built TestApp.io to solve the pain of app distribution for mobile app development teams.

Join our community for feedback and support.

Happy releasing 🎉

Azure Pipeline allows you to build and upload both Android and iOS apps to TestApp.io for testing and feedback. Here's how to do it:

iOS

To integrate TestApp.io with Azure Pipeline for iOS, follow these steps:

1. Clone the sample project testappio-ios-sample-app from GitHub and switch to the integration-azure branch:

git clone https://github.com/testappio/ios-sample-app.git
git checkout integration-azure

2. Configure the iOS project for Fastlane:

• Install Fastlane.
• Create a ./Gemfile file in the root directory of your project with the following content:

source "https://rubygems.org"
gem "fastlane"

• Run bundle update and add both the ./Gemfile and the ./Gemfile.lock files to version control.
• Initiate Fastlane by running the following command in the iOS project folder:

bundle exec fastlane init

• Follow the wizard; it will create a ./fastlane/Appfile file with your Apple ID and team.
• Initiate Match by running the following command:

bundle exec fastlane match init

• Follow the instructions and provide the new empty git repository when asked; it will create the Matchfile.

• Generate the certificate and provisioning profile by running the following command:

bundle exec fastlane match adhoc

• Provide a matching password for encrypting the certificates and profiles in the GIT repository.

• Add the testappio plugin for Fastlane by running the following command:

bundle exec fastlane add_plugin testappio

3. Select provisioning profiles in Xcode:

The newly created certificates and profiles should now be possible to select inside your project. Open Xcode and go to Signing & Capabilities.

4. Set up Azure Pipeline:

• Create an Azure Pipeline and select the pipeline configuration file created in the previous step.

• Configure MATCH_PASSWORD secret variable for the pipeline.

• Similarly, configure GITHUB_API_TOKEN the secret variable for the pipeline by navigating to Tokens and generating a Personal Access Token.
• Add TESTAPPIO_API_TOKEN and TESTAPPIO_APP_ID as secret variables for the TestApp.io Fastlane plugin. You can grab them from your App -> Integrations.

5. Create the lane:

Create a ./fastlane/Fastfile file and copy the following content:

default_platform(:ios)

platform :ios do
  desc "Build the adhoc and upload to TestApp.io"
  lane :beta do
    match(type: "adhoc")
    gym(export_method: "ad-hoc")
    upload_to_testappio(
      release_notes: "My release notes here...",
      git_release_notes: true,
      git_commit_id: false,
      notify: true
    )
  end
end

More info on the Fastlane plugin: https://help.testapp.io/fastlane-plugin/#testappio-actions

Note that you may already have your lane in place. Copy the upload_to_testappio action and put it into your pipeline after the IPA export.

Here's the Azure Pipeline configuration file:

trigger:
- main

pool:
  vmImage: macOS-12

steps:
- script: |
    bundle install
    bundle exec fastlane ios beta
  displayName: 'Execute the lane'

6. Commit and push the change to trigger the pipeline.

Android

To integrate TestApp.io with Azure Pipeline for Android, follow these steps:

1. Clone the sample project android-sample-app from GitHub and switch to the integration-azure branch:

git clone https://github.com/testappio/android-sample-app.git
git checkout integration-azure

2. Configure the Android project

• Install Fastlane.
• Create a ./Gemfile file in the root directory of your project with the following content:

source "https://rubygems.org"
gem "fastlane"

• Run bundle update and add both the ./Gemfile and the ./Gemfile.lock files to version control.
• Initiate Fastlane by running the following command in the Android project folder:

bundle exec fastlane init

• Follow the wizard; it will create a ./fastlane/Appfile file with the required information.

3. Set up Azure Pipeline:

• Add TESTAPPIO_API_TOKEN and TESTAPPIO_APP_ID as secret variables for the TestApp.io Fastlane plugin. You can grab them from your App -> Integrations.

4. Create the lane:

Create a ./fastlane/Fastfile file and copy the following content:

default_platform(:android)

platform :android do
  desc "Build and upload to TestApp.io"
  lane :beta do
    gradle(
      task: "assemble",
      build_type: "Release"
    )
    upload_to_testappio(
      release_notes: "My release notes here...",
      git_release_notes: true,
      git_commit_id: false,
      notify: true
    )
  end
end

More info on the Fastlane plugin: https://help.testapp.io/fastlane-plugin/#testappio-actions

Note that you may already have your lane in place. Copy the upload_to_testappio action and put it into your pipeline after the APK export.

Here's the Azure Pipeline configuration file:

trigger:
- main

pool:
  vmImage: ubuntu-22.04

steps:
- script: |
    bundle install
    bundle exec fastlane android beta
  displayName: 'Execute the lane'

5. Commit and push the change to trigger the pipeline.

That's it! Now you can build and upload your Android and iOS apps to TestApp.io for testing and feedback using Azure Pipeline.

Feedback & Support

Developers built TestApp.io to solve the pain of app distribution for mobile app development teams.

Join our community for feedback and support.

Happy releasing 🎉

Troubleshooting App Signing with the App Store Distribution Profile

It needs to be unclear and clarified when trying to sign an App correctly for submission to the App Store and having problems. You might be signed in with the App Store distribution profile.

What is the App Store Distribution Profile?

The App Store Distribution Profile is the set of credentials associated with your App Store account. It connects your app to the App Store and shares it with other Apple accounts.

What should I do if I have an App Store Distribution Profile?

If your application has been signed using the App Store distribution profile, please upload a signed IPA file using either an Ad-Hoc or Enterprise provisioning profile.

Do you know where I can find more help?

For more detailed information about signing your app for submission to the App Store, please visit the Apple Developer Portal.

Related Articles:

How to get UDID?

Get UDID from testers

Help CenterOmar Masad

How to add UDID to Apple Developer Account?

Find Your UDID Using Apple Music App - Find UDID Using Xcode - Find Your UDID Using TestApp.io - Register UDID With A Developer account

Help CenterOmar Masad

Before you can put your app into the world, you need to ensure it’s properly signed with a provisioning profile.

But what is a provisioning profile, and why does it matter? In this blog post, we’ll look at what provisioning profiles are and how they affect the success of an app.

Ad-Hoc vs. Enterprise Provisioning Profiles:

Ad-Hoc and Enterprise provisioning profiles are two different types of profiles that serve different purposes.

Ad-Hoc provisioning profiles are used when distributing an app to a limited number of devices for testing purposes.

These profiles limit the number of devices the app can install to 100, making it ideal for internal testing or distributing beta versions to select testers.

On the other hand, Enterprise provisioning profiles are used to distribute apps to employees of a specific organization. These profiles allow the app to be installed on any device registered under the organization's Apple Developer account, making it suitable for in-house distribution.

Obtaining Provisioning Profiles:

To obtain an Ad-Hoc or Enterprise provisioning profile, a developer must first enroll in the Apple Developer Program. Once enrolled, they can create and manage profiles through the Apple Developer portal.

For Ad-Hoc profiles, developers must add the UDID numbers of the devices they wish to distribute the app. For Enterprise profiles, they need to register their organization and obtain a DUNS number.

How to get UDID?

Get UDID from testers

Help CenterOmar Masad

How to add UDID to Apple Developer Account?

Find Your UDID Using Apple Music App - Find UDID Using Xcode - Find Your UDID Using TestApp.io - Register UDID With A Developer account

Help CenterOmar Masad

Using the Appropriate Development Profile:

When developing an app, it's essential to use the appropriate development profile for the intended distribution method. If the wrong profile is used, the app may not install or function correctly, causing frustration for both the developer and end-users.

Developers should also ensure that their provisioning profiles are up-to-date and valid. Provisioning profiles typically expire after a certain period, so updating them regularly is crucial.

What is a Provisioning Profile?

A provisioning profile is a digital certificate that links apps to the Apple Developer Program.

A valid provisioning profile ensures that an authorized developer or organization created any app released on Apple’s App Store.

It also ensures that the app was built using the same code as the version submitted to Apple for review.

Why Do Provision Profiles Matter?

Provision profiles are important because they allow developers to control which devices their apps can be installed on.

For example, if a developer wants to make their app available only to internal employees of their company, they can create an Enterprise provision profile that will limit access to those specific users.

On the other hand, if a developer wants their app to be available for anyone in public to download from the App Store, they would need to create an Ad-Hoc or Developer profile instead.

In addition, when developing an app, developers must use a valid provisioning profile during every step of the process, or else their testers won’t be able to install it on their devices.

If your testers receive an error message stating, “The provisioning profile used has expired,” then either your current IPA is not signed with a valid Ad-Hoc or Enterprise profile, or it is not linked with a non-expired certificate.

To resolve this issue, upload a new IPA file that has been appropriately signed with either type of profile and includes all applicable information, such as UDID numbers and bundle IDs, before submitting it for final review.

Conclusion:  

In conclusion, provisioning profiles are an essential aspect of iOS app development that controls which devices an app can be installed.

By using the appropriate Ad-Hoc or Enterprise profile and ensuring it's up to date, developers can streamline the app development process and ensure a smooth distribution experience for their users.

No longer using TestApp.io? You can permanently delete your account in a few steps.

What you'll need

• Every member role can delete their TestApp.io account.
• Owners of Teams with more than one member must assign another team Owner or remove everyone from the team and leave the group.

Delete your account

You can delete your TestApp.io account using the mobile app and portal.

To delete your account:

1. From Mobile App

   • Left side menu
   • Account & Settings
   • Scroll to the bottom of the screen and tap on Delete Account
   • Read the confirmation message
   • Submit Request

2. From Portal

   • Click on the user icon in the top menu
   • Edit Profile
   • Scroll to the bottom of the screen and click on Delete Account
   • Read the confirmation message
   • Submit Request

Your account will be scheduled for deletion within 24 hours. That includes:

1. Your personal information: Name, email, and login
2. Your name in app releases,  app feedback, and similar features will be renamed to "Deleted User."

Things will stay in your teams:

1. Your app releases
2. Your app feedback

Feedback & Support

Developers built TestApp.io to solve the pain of app distribution for mobile app development teams.

Join our community for feedback and support.

Happy releasing 🎉

Bitrise CI pipeline allows you to build and upload both Android & iOS apps to TestApp.io to notify your testers for testing and feedback.

iOS

We will demonstrate with our sample project testappio-ios-sample-app to integrate TestApp.io with Bitrise CI.

1. Clone the project repository and checkout the integration-bitrise branch:

git clone https://github.com/testappio/ios-sample-app.git
git checkout integration-bitrise

2. Configure the iOS project for Fastlane:

• Install Fastlane.
• Create a ./Gemfile file in the root directory of your project with the following content:

source "https://rubygems.org"
gem "fastlane"

• Run bundle update and add both the ./Gemfile and the ./Gemfile.lock files to version control.
• Initiate Fastlane by running the following command in the iOS project folder:

bundle exec fastlane init

• Follow the wizard; it will create a ./fastlane/Appfile file with your Apple ID and team.
• Initiate Match by running the following command:

bundle exec fastlane match init

• Follow the instructions and provide the new empty git repository when asked; it will create the Matchfile.

Generate the certificate and provisioning profile by running the following command:

bundle exec fastlane match adhoc

• Provide a matching password for encrypting the certificates and profiles in the GIT repository.

• Add the testappio plugin for Fastlane by running the following command:

bundle exec fastlane add_plugin testappio

3. Select provisioning profiles in Xcode:

The newly created certificates and profiles should now be possible to select inside your project. Open Xcode and go to Signing & Capabilities.

4. Setup Bitrise:

• Configure MATCH_PASSWORD the secret parameter in Bitrise.
• Go to your Bitrise project page, then Workflow, and add a Secret parameter MATCH_PASSWORD.
• Configure GITHUB_API_TOKEN secret parameter in Bitrise CI.
• Navigate to Tokens to generate a Personal Access Token, and create a GITHUB_API_TOKEN secret in Bitrise CI. This is for accessing the private certificates' repository.
• Add secret parameters for testappio Fastlane plugin.
• Add TESTAPPIO_API_TOKEN and TESTAPPIO_APP_ID to Bitrise secret parameters. You can grab them from your App -> Integrations.

5. Run the pipeline:

Create the lane by creating ./fastlane/Fastfile with the following content:

default_platform(:ios)

platform :ios do
  desc "Build the adhoc and upload to TestApp.io"
  lane :beta do
    match(type: "adhoc")
    gym(export_method: "ad-hoc")
    upload_to_testappio(
      release_notes: "My release notes here...",
      git_release_notes: true,
      git_commit_id: false,
      notify: true
    )
  end
end

More info on the Fastlane plugin: https://help.testapp.io/fastlane-plugin/#testappio-actions

have your lane in place; copy the upload_to_testappio action and put it into your pipeline after the IPA export.

6. The Bitrise pipeline:

Create or update bitrise.yml a file under your project root folder. Or update your bitrise.yml accordingly, if you have the bitrise.yml file stored and managed on bitrise.io.

---
format_version: '11'
default_step_lib_source: 'https://github.com/bitrise-io/bitrise-steplib.git'
project_type: ios
app:
  envs:
  - FASTLANE_XCODE_LIST_TIMEOUT: '120'
  - opts:
      is_expand: false
    FASTLANE_WORK_DIR: .
  - opts:
      is_expand: false
    FASTLANE_LANE: ios development
  - opts:
      is_expand: false
    TESTAPPIO_NOTIFY: 'true'
  - opts:
      is_expand: false
    MATCH_SKIP_CERTIFICATE_MATCHING: 'true'
workflows:
  primary:
    steps:
    - activate-ssh-key@4:
        run_if: '{{getenv "SSH_RSA_PRIVATE_KEY" | ne ""}}'
    - git-clone@6: {}
    - script@1:
        inputs:
        - content: |-
            #!/usr/bin/env bash
            # fail if any commands fails
            set -e
            # debug log
            set -x

            # write your script here
            echo "machine github.com login $GITHUB_API_TOKEN" >> ~/.netrc
    - fastlane@3:
        inputs:
        - lane: $FASTLANE_LANE
        - work_dir: $FASTLANE_WORK_DIR
meta:
  bitrise.io:
    stack: osx-xcode-13.2.x
    machine_type_id: g2.4core
trigger_map:
- push_branch: main
  workflow: primary

7. Commit and push the change to trigger the Bitrise pipeline.

Android

Sample project we used for following instructions, android-sample-app.

1. Clone the project repository and checkout the integration-bitrise branch:

git clone https://github.com/testappio/android-sample-app.git
git checkout integration-bitrise

2. Configure the Android project for Fastlane:

• Install Fastlane.
• Create a ./Gemfile file in the root directory of your project with the following content:

source "https://rubygems.org"
gem "fastlane"

• Run bundle update and add both the ./Gemfile and the ./Gemfile.lock to version control.
• For more details please see Setup Fastlane.

3. Init Fastlane:

In the Android project folder, run:

bundle exec fastlane init

And follow the wizard; it will create ./fastlane/Appfile with the required information.

4. Setup Bitrise:

• Add secret parameters for testappio Fastlane plugin.
• Add TESTAPPIO_API_TOKEN and TESTAPPIO_APP_ID to Bitrise secret parameters. You can grab them from your App -> Integrations.

5. Run the pipeline:

Create or update bitrise.yml file under your project root folder. Or update your bitrise.yml accordingly, if you have the bitrise.yml file stored and managed on bitrise.io.

---
format_version: '11'
default_step_lib_source: 'https://github.com/bitrise-io/bitrise-steplib.git'
project_type: android
app:
  envs:
  - FASTLANE_XCODE_LIST_TIMEOUT: '120'
  - opts:
      is_expand: false
    FASTLANE_WORK_DIR: .
  - opts:
      is_expand: false
    FASTLANE_LANE: android beta
workflows:
  primary:
    steps:
    - activate-ssh-key@4:
        run_if: '{{getenv "SSH_RSA_PRIVATE_KEY" | ne ""}}'
    - git-clone@6: {}
    - fastlane@3:
        inputs:
        - lane: $FASTLANE_LANE
        - work_dir: $FASTLANE_WORK_DIR
meta:
  bitrise.io:
    stack: linux-docker-android-20.04
    machine_type_id: elite
trigger_map:
- push_branch: main
  workflow: primary

6. Commit and push the change to trigger the Bitrise pipeline.

Feedback & Support

Developers built TestApp.io to solve the pain of app distribution for mobile app development teams.

Join our community for feedback and support.

Happy releasing 🎉

Feedback & Support

Developers built TestApp.io to solve the pain of app distribution for mobile app development teams.

Join our community for feedback and support.

Happy releasing 🎉