flutter_flavorizr
flutter_flavorizr copied to clipboard
iOS Config not working [APP NAME]
Everything is working fine for me when running on Android, but iOS is not working as expected (at least as I expect, maybe I am wrong). I am creating an app with two flavors, different app names and icons. Android shows both icons and names correctly, however, iOS just changes the icon, but shows the same name on both apps. To fix this, I have to change "Bundle display name" in Runner info config (xcode) to a User defined Setting, and manually give a name to each run config.
Is this the expected behaviour or should flavorizr make this config for me (as it does on Android)?
Thx in advance for the help and congrats for the useful package!
I attach my flavorizr config on pubspec.yaml
flavorizr:
ide: "idea"
app:
android:
flavorDimensions: "flavor-type"
ios:
flavors:
parla:
app:
name: "Parla"
icon: "assets/images/parla/logo.jpg"
android:
applicationId: "com.example.parla"
icon: "assets/images/parla/logo.jpg"
ios:
bundleId: "com.example.parla"
icon: "assets/images/parla/logo.jpg"
zamora:
app:
name: "Zamora"
icon: "assets/images/zamora/logo.jpg"
android:
applicationId: "com.example.zamora"
icon: "assets/images/zamora/logo.jpg"
ios:
bundleId: "com.example.zamora"
icon: "assets/images/zamora/logo.jpg"
Hi @pbayog00, Check this issue
https://github.com/AngeloAvv/flutter_flavorizr/issues/97
Hi @DattatreyaReddy, I see what you mean. That issue in fact is helpful, but it doesn't solve the problem I have. I mean, I can manually change the 'Bundle display name' variable to $(BUNDLE_NAME) and that saves me from having to create a user-defined variable and set the app names one by one per config. However, I do have to modify the info.plist by myself, and I thought this could be avoided, as it is on android, especially given that it is a very simple modification. Thank you for your answer.
Hi @DattatreyaReddy, I see what you mean. That issue in fact is helpful, but it doesn't solve the problem I have. I mean, I can manually change the 'Bundle display
It's true and thats a feature request in the above issue, So, i just want to inform you about a work around for now.
Thank you very much for your help, I'll keep up to date for the feature