fastlane: invalid option: --env=staging
Since updating from 2.147.0
to 2.148.0
I now receive: invalid option: --env=staging
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 5
- Comments: 19 (8 by maintainers)
Since updating from 2.147.0
to 2.148.0
I now receive: invalid option: --env=staging
I am using the Microsoft Task for Azure DevOps Pipelines that does something like this:
and failed with:
Strangly in the command line there is no env parameter so I don’t know why it fails with this error. But maybe the output is only a log and is not the command line that is called underneith.
The Task is available here: https://github.com/microsoft/app-store-vsts-extension
In their Repository there is also an issue open to this problem: https://github.com/microsoft/app-store-vsts-extension/issues/152
As a workaround I configure the task to only ever install 1.147.0 instead of the newest version which currently works.
I think we now have to use
fastlane action --env staging
Yes, confirmative. Just remove the
=
do the trick.Yes @liamnichols it was about
--env=foo
. So basicallyfastlane some_lane_using_dotenv --env=foo
@alubeck: Which command had you been running with
--env=foo
prior to this failing? I’m curious as I authored the change that probably caused this regression so sorry about that