> Having different build targets (dev/release) in Podfile is not possible
It is very much possible and used in every cocoapods based app.
Currently example app have 3 targets for dev build, test build and functional tests.
We can just introduce another target for production.
Pods can also use external source code have different values depending on the env variables etc. Definition can use some subsets of ruby source code.
We can have separate or even nested targets/subtargets.
Happy to show how this works.
Best way to do it is to have different targets reflecting different versions.
This is typical for IOS development to define targets like production/development/testing and have different values associated with that. We have done that on JS (where we shadow production artifacts for development) and on Android (using different profiles for prod and dev) |
|
