Create dedicated target instead of new build configuration file

[EArminjon]

I'm not an Apple Expert and i didn't know if this package follow the right way to use flavors or if my hint is incorrect.

Context

I've setup a huge project using more than 70 build configuration file (without this package) and i saw that Xcode don't support that well, it became very laguy after some years and it's hard today to rework the Xcode part manually. That's why i take a look on this package.

Sadly, this package did same as us, it stay on the current Runner Target and create additional Configuration files.

Xcode was very slow because, each time Xcode open a tab or change a settings, Xcode try to load / reload everything on the current Target.
Has i got 70 build configuration, each Xcode property was overridable by 70 entries and that was maybe the issue. CPU usage 100% (Mac Book Pro M1, other laptop just crash or took 1 hour).

I've talked with some iOS native developers and they show me a different way (the correct one ?) to use define flavors, they show me the usage of Targets.

It will require to duplicate other targets dedicated for Notification, LiveActivity (etc.) for each flavors but if it's the right way, we should maybe follow... ?

How it will work :

Each target (Banana, Apple) has it's own Build Settings so we can well override what we want.
Each scheme should point to the right executable and build the right targets only (Banana, BananaNotification, BananaLiveActivities, ...). Maybe, the flavorizr.yaml will need add a new entry to know that.
Configuration files will stay as the flutter default ones Debug, Profile, Release. No need to duplicate them.

Feedback and needs

What do you think about it ?

Do you think it's possible to support this ? It will be major breaking change if so, but performance benefits can be a good goal.

Issue open : #314

[JohnettJobben1]

@AngeloAvv Would you mind sharing your thoughts on this, if possible?

[JohnettJobben1]

@EArminjon @AngeloAvv Does ios:buildTargets cover this use case?

[AngeloAvv]

Hey @EArminjon , here are my thoughts.

With this proposal, we might tackle extension-related problems, so I'm very interested in considering this solution.

Having said that, a few questions for you:

• This way of handling targets is not the recommended way according to the Flutter docs. I would feel more confident if we could discuss with the Flutter team or at least someone who worked on the iOS side of Flutter flavors.
• Ok about build settings, but what about other parameters like variables? If you no longer rely on custom xcconfig files, what could be the best way of handling them?

[EArminjon]

For variables, maybe we can create "User-Defined settings" inside project's build settings for globals or inside Target's build settings for others.

I totally agree with you : i will be very helpful to have the vision of an iOS expert on this subject.

[swetav1996]

Error: The Xcode project does not define custom schemes. You cannot use the --flavor option.

Exited (1).
Do I need to create scheme manually to use this package