fastlane: setting FASTLANE_SKIP_UPDATE_CHECK env variable does not prevent update check
New Issue Checklist
- Updated fastlane to the latest version
- I read the Contribution Guidelines
- I read docs.fastlane.tools
- I searched for existing GitHub issues
Issue Description
Complete output when running fastlane, including the stack trace and command used
You can use:
--capture_outputas the last commandline argument to get that collected for you
[INSERT OUTPUT HERE]
Environment
Please run fastlane env and copy the output below. This will help us help you 👍
If you used --capture_output option please remove this block - as it is already included there.
[INSERT OUTPUT HERE]
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 25 (9 by maintainers)
@jrreed @chnbz Made a fix for this here - #12338
Heyyyyyy 👋 Thanks for commenting on this! This will be fixed in
2.86.0(which should be released early this week) with my PR that loadsdotenvfaster - https://github.com/fastlane/fastlane/pull/12047Didn’t know this issue existed otherwise I would have mentioned it in my PR 😊
Hey everyone, I took a quick look, and I can confirm this is a bug, and it’s not something you’re doing wrong.
It’s a fastlane bug that can be resolved, the problem is: We start looking for updates here, and then at a later stage, we load the
.envfiles over here.This requires some refactoring to make the order correct. It’s not something I can do right now, however feel free to jump in a submit a PR for it. I marked the issue as “you can do this” 👍
For now, there seems to be multiple rather easy workarounds, one of which is to add
FASTLANE_SKIP_UPDATE_CHECKto your global shell environment. I can see how this might not be 100% ideal, but it should do the job for now.I hope that helps, and sorry I won’t be able to do the refactor myself right now