How to properly setup fastlane match with bitrise.io?


#1

How to properly setup fastlane match with bitrise.io?

Fastlane Match requires a repo access to obtain certificates?

I added ssh key from bitrise workflow to bitbucket to give read only access but was to only be left with the following error:

I’m having no issues with fastlane deployements to testflight directly and no errors when I run bitrise run primary command. It is only happening for when I run bitrise.io CI/CD that I get this error. Why is this? And how can I quickly resolve this issue thanks?


#2

Hey @aznric3boi :wave:

You can find the related guide at https://devcenter.bitrise.io/tutorials/fastlane/how-to-configure-fastlane-match-for-bitrise/

If you’d have any questions just let us know! :wink:


#3

@viktorbenei Thanks!

I keep running into the following error with an sms ping to my connected iOS devices but unable to enter in the number and my entire build fails. Would appreciate your feedback.

Are my secret environment variables not being exposed properly for bitrise? I’m really confused and going in circles.


#fastlane match 
match(git_url: <git@bitbucket.org.....git>,
        type: 'appstore',
        app_identifier: 'com.mydomain.myapp')


 ---
format_version: '6'
default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git
project_type: fastlane
app:
  envs:
  - FASTLANE_XCODE_LIST_TIMEOUT: '120'
  - opts:
      is_expand: false
    FASTLANE_WORK_DIR: "."
  - FASTLANE_LANE: ios beta_testflight
trigger_map:
- push_branch: "*"
  workflow: primary
- pull_request_source_branch: "*"
  workflow: primary
workflows:
  primary:
    steps:
    - activate-ssh-key@4.0.3:
        run_if: '{{getenv "SSH_RSA_PRIVATE_KEY" | ne ""}}'
    - git-clone@4.0.11: {}
    - script@1.1.5:
        title: Do anything with Script step
    - certificate-and-profile-installer@1.10.1: {}
    - fastlane@2.3.12:
        inputs:
        - lane: "$FASTLANE_LANE"
        - work_dir: "$FASTLANE_WORK_DIR"
    - deploy-to-bitrise-io@1.3.15: {}
    envs:
    - opts:
        is_expand: false
      FASTLANE_USERNAME: ''

References:


https://docs.fastlane.tools/best-practices/continuous-integration/#two-step-or-two-factor-auth


#4

Hi @aznric3boi!

Could you please also include a build URL of what you’re experiencing exactly we could look into?


#5

697d534597a7dcec


#6

Hy there @aznric3boi! the only thing I found that could cause this issue is this line:

Your session cookie has been expired.```