Additions to the fastlane Appfile? about produce HOT 5 CLOSED

Not sure honestly. It should be a Producefile, which wouldn't make a lot of sense, since it's changing every time anyway.
How would you use it differently?

from produce.

It just seems that it would make sense to have one file which specifies all the options for an app which could be read by all the fastlane tools. Tools would then specify the location of that file so they could have different settings if required but most tools would use the same file/information. Having duplicate data repeated and search-and-replaced across multiple files seems less than ideal, although it works fine.

from produce.

In my case, I generate the .env file with a lot of information and reference them in the Deliverfile and Fastfile with ENV["CUSTOM_VAR"].

from produce.

I'll close this issue for now, as the configuration is stored in the Fastfile. Thanks for your feedback 👍

from produce.

This issue was migrated to fastlane/fastlane#3088. Please post all further comments there.

fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀

from produce.