At this time, you need to use fastlane for a couple of tasks on your local dev machine:
When running match to generate certs and profiles.
When you want to change the environment to production, testing, or dev.
Proposed idea
We cannot fix the match issue. That is just going to be needed. No big deal.
For changing the environment and such, however, I find this to be important that it works without the need of fastlane.
Setting the environment right now does a few things.
Reads values from .env and changes the project up. Setting bundle ID, app name, dynamic links domain, etc. Mostly setting plist entries.
To fix this, we need to change how we approach this. Thinking we can create a CLI you install via cocoapods? Running CLI binaries works well with XCode and we need this setting of the environment to run on every build in XCode.
At this time, you need to use fastlane for a couple of tasks on your local dev machine:
matchto generate certs and profiles.Proposed idea
We cannot fix the
matchissue. That is just going to be needed. No big deal.For changing the environment and such, however, I find this to be important that it works without the need of fastlane.
Setting the environment right now does a few things.
To fix this, we need to change how we approach this. Thinking we can create a CLI you install via cocoapods? Running CLI binaries works well with XCode and we need this setting of the environment to run on every build in XCode.
cici decrypt. this issue talks about this