New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[match] undefined local variable or method profile
when running match with output_path
#21945
Comments
undefined local variable or method
profile' when running match with
output_path`profile
when running match with output_path
@nekrich This would seem to have been introduced here: https://github.com/fastlane/fastlane/pull/21691/files#diff-8cd09d7ab3f4398e3160f603839ac2891e3cdf60e7f09930a1288ce33ab8fc1fR359 |
I've been scratching my head all morning trying to see what was the problem, I'm glad I'm not the only one or the runner. Can someone please add a fix for this? Deployment is paused because of this |
#21946 is now ready for review |
Hi guys, anyone here? I still got the issue. I'm running it on self-hosted (MacBook M1 Pro) github action. |
Same issue with match on my end as well (still) |
New Regression Checklist
Regression Information
Regression Description
As of the 2.220.0 release, I'm unable to run
match
in CI. Near as I can tell, I hit aundefined local variable or method
profile`` simply on account of using theoutput_path
option.Relevant match action:
Complete output when running fastlane, including the stack trace and command used
Environment
The text was updated successfully, but these errors were encountered: