Replies: 1 comment
-
Hey @ytneu , some processors need other processors to be executed before they can step in. Some of them need base files that are downloaded from the processor assets:download and that's why running flutter_flavorizr without defining a custom set of instructions works properly. This is something I'm gonna change in the next major release as this leads to confusion among flutter_flavorizr users |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Angelo,
First of all I want to say this package is super cool, it makes setting flavors pretty straightforward, thanks for that!
Since my app is extending from mobile to desktop I've started setting up the macos flavors. Here are my steps:
(flutter_flavorizr: 2.2.3)
macos
props to mypubspec.yaml
dart run flutter_flavorizr
dart run flutter_flavorizr
and started running processes one after another.dart run flutter_flavorizr -p macos:xcconfig
, as for the reference I've opened configs from/ios
directory, which looks likebut as I checked
/macos
generated xconfigs they all look like thisNothing more is seen, I guess it's issue? I didn't find the answear, so I decided to just copy paste those file from
/ios
to/macos
6) Next step was:
dart run flutter_flavorizr -p macos:configs
, unfortunately this step exits with error, (which is surprising for me since generaldart run flutter_flavorizr
command works without any problems), at this point I have no clue what's going on:It would be lovely to get some insights, what's wrong with me reasoning and where did I make mistake. Since I can confirm running straight
dart run flutter_flavorizr
works fineBeta Was this translation helpful? Give feedback.
All reactions