[Match] No value found for 'git_url'

[geeklingo]

New Issue Checklist

• [x] Updated fastlane to the latest version
• [x] I read the Contribution Guidelines
• [x] I read docs.fastlane.tools
• [x] I searched for existing GitHub issues

Issue Description

Using fastlane to build and deploy an XCode project (exported from Unity). When match is run, the following error is received:

No value found for 'git_url'

Command executed

bundle exec fastlane match

Running the command on my local machine works fine but when running via GitLab i keep getting that error. The git_url is in my matchfile which is in my fastlane folder. It all works as it runs locally fine. Just not remotely via the CI\CD pipeline. I'm not using environment variables for this.

The relevant section from my gitlab-ci.yml

deploy-ios:
 stage: deploy
 script:
   - cd $UNITY_DIR/Builds/iOS/$BUILD_NAME
   - bundle update
   - bundle exec fastlane match <- This is where it's failing
   - bundle exec fastlane run set_info_plist_value path:"./Info.plist" key:"CFBundleShortVersionString" value:"0.1.0"
   - bundle exec fastlane ios beta
 tags:
   - ios
   - mac
 needs: ["build-ios-xcode"]
 # Only deploy if "deploy" is in the tag
 rules:
   - if: '$CI_COMMIT_TAG =~ /^deploy.*/i'

Matchfile

git_url("https://gitlab.com/xxxx/xxxx")
storage_mode("git")

type("appstore") # The default type, can be: appstore, adhoc, enterprise or development
app_identifier(["bundleid"])
username("username") # Your Apple Developer Portal username

type("development") # The default type, can be: appstore, adhoc, enterprise or development
app_identifier(["bundleid"])
username("username") # Your Apple Developer Portal username

[fastlane-bot]

It seems like you have not included the output of fastlane env To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env :+1:

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself :muscle:

This issue will be auto-closed if there is no reply within 1 month.

[instanceof-inf]

@geeklingo did you manage to get past this? I am sitting with roughly the same issue now

[geeklingo]

Yeah, had to update to the latest Gitlab runner.