Fastlane Boarding支持Fabric Beta测试吗？求配置及网页搭建流程

Great question! Let's break down everything you need to know about using Fastlane Boarding with Fabric Beta:

1. Does Fabric Beta Support Fastlane Boarding? #

Absolutely! Fastlane Boarding works smoothly with Fabric Beta (even though Fabric Beta is now integrated into Firebase App Distribution, legacy setups are fully compatible). Boarding acts as a self-hosted web portal that lets your testers sign up and install your Fabric Beta builds without needing direct access to TestFlight or the Fabric dashboard.

2. Configuration for Fabric Beta + Fastlane Boarding #

First, make sure you have Fastlane installed and your Fabric Beta credentials ready (you can grab your API key and build secret from your Fabric dashboard). Here's how to set up the integration:

Prerequisites #

• Install Fastlane: gem install fastlane
• Have your Fabric API key and build secret on hand
• Ensure your project is set up for Fastlane (run fastlane init if you haven't already)

Step-by-Step Configuration #

• Add the Boarding plugin to your Fastlane setup:
  Run this in your project directory:

  fastlane add_plugin boarding
  

• Update your Fastfile to link Fabric Beta and Boarding:
  Here's a sample snippet to build, upload to Fabric Beta, and configure Boarding. Adjust the values to match your app:

  lane :beta_distribution do
    # Build your iOS app (modify for Android if needed)
    gym(scheme: "YourAppScheme")
    
    # Upload the build to Fabric Beta
    fabric(
      api_key: "YOUR_FABRIC_API_KEY",
      build_secret: "YOUR_FABRIC_BUILD_SECRET",
      notes: "New beta build: fixed login bug and updated UI",
      groups: ["Internal Testers", "External Beta Users"] # Your tester groups
    )
    
    # Generate the Boarding portal (optional, to auto-generate access)
    boarding(
      app_identifier: "com.yourcompany.yourapp",
      beta_distribution: "fabric" # Tells Boarding to use Fabric Beta
    )
  end
  

• Set required environment variables:
  You'll need these variables to connect Boarding to Fabric Beta. You can set them in your shell or add them to a .env file in your project:
  • FABRIC_API_KEY: Your Fabric API key
  • FABRIC_BUILD_SECRET: Your Fabric build secret
  • BOARDING_APP_IDENTIFIER: Your app's bundle ID (iOS) or package name (Android)

3. Self-Hosting the Fastlane Boarding Portal for Fabric Beta #

If you want to host your own web portal for testers to access Fabric Beta builds, follow these steps:

Step 1: Get the Boarding Source Code #

Obtain the Fastlane Boarding source code (via official Fastlane resources), then navigate to its directory in your terminal:

cd boarding

Step 2: Install Dependencies #

Install the required Ruby gems for Boarding:

bundle install

Step 3: Configure Environment Variables #

Create a .env file in the root of the Boarding directory, and add these values (replace with your own):

FABRIC_API_KEY=your_fabric_api_key_here
FABRIC_BUILD_SECRET=your_fabric_build_secret_here
BOARDING_APP_IDENTIFIER=com.yourcompany.yourapp
BOARDING_TITLE="Your App's Beta Testing Portal" # Customize the portal's display title

Step 4: Test the Local Server #

Start the local Boarding server to make sure everything works:

bundle exec rackup

Your portal will be available at http://localhost:9292. Testers can visit this page, enter their email, and get a link to install the latest Fabric Beta build.

Step 5: Deploy to a Production Server #

To make the portal accessible to your testers publicly, deploy it to a hosting platform like Heroku, AWS Elastic Beanstalk, or DigitalOcean. For example, deploying to Heroku:

• Create a Heroku app: heroku create your-custom-boarding-portal
• Set the environment variables on Heroku:

  heroku config:set FABRIC_API_KEY=your_key FABRIC_BUILD_SECRET=your_secret BOARDING_APP_IDENTIFIER=your_bundle_id BOARDING_TITLE="Your App Beta Portal"
  

• Push the Boarding code to Heroku to deploy: git push heroku main

内容的提问来源于stack exchange，提问作者subodh1989