-
I used to use script build phase for this on kotlin version
It is somewhat inspired by the futured template But since updating to kotlin to version
I tried switching to any other task like Upon reverting back to original versions it turns out that the flavor is also not set when using other tasks instead of So the question is:What other task can I use to set the multiplatform flavor from XCode target's build phases instead since the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Ok, so I finally figured it out. Running Intended way (as I understand it):
|
Beta Was this translation helpful? Give feedback.
Ok, so I finally figured it out.
Running
embedAndSign
task in a CocoaPods project to set agradle.property
is wrong. As discussed in the original issue, it can lead to linking issues and generally does not make much sense, as theshared
module is already build as a pod.Intended way (as I understand it):
Edit iOS configurations to contain the flavor name (e.g.
ProdDebug
). It can be done in project settings under the Info tab. CocoaPods should then automatically create corresponding configuration files under thePods
folder.Edit your scheme for each target to run the corresponding configuration.
The configuration name is then automatically passed to the gradle when building the modu…