Angelo Cassano
Angelo Cassano
Thank you @andre-stefanov for providing a solution to this issue
Hey @lucavenir , yes I can try. In the meantime, you could add a dependency_overrides in your pubspec.yaml hoping everything works fine
Duplicate of #10
Hello @kareemzok , can you provide the instructions you are using to compile the aab bundle?
> Hello @kareemzok , can you provide the instructions you are using to compile the aab bundle? Still a valid question :)
Can you try using a manual approach, in particular by building your artifact using: `flutter build appbundle --flavor apple -t lib/main-apple.dart --release ` and then by signing the generated bundle...
Hello @p02diada , can you please provide your flavorizr section from the pubspec.yaml file? Did you install ruby, gem and xcodeproj?
> Hello @AngeloAvv I just start using your package and faced with same issue for iOS. Could you check this issue please? > > Configuration: > > ```yaml > flavorizr:...
Just copy an existing one from one of your flavors as a permanent workaround, I will fix this problem ASAP
Hi @dJani97 , according to the [official documentation](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundledisplayname), you should use CFBundleDisplayName only if your app name is longer than the CFBundleName. Can you please elaborate your thoughts?