request: flutterfire configure needs a new option for app nickname

[frederikstonge]

Is there an existing feature request for this?

• I have searched the existing issues.

Command

flutterfire configure -n / --name <app_name>

Description

As a developer, I want to be able to specify the name of the app to be created when calling flutterfire configure. Right now, it is defaulting to the value in pubspec.yaml.

Reasoning

I am running multiple flavors and I created a script to automatically create all apps in firebase. I want to specify the name of each app without them taking the value from pubspec.yaml.

Additional context and comments

No response

[russellwheatley]

I am confused, what would be updated by having an option for the app nick name?

[black-rusuz]

@russellwheatley This is a good feature. I use futterfire configure in a CI/CD pipeline to build different applications using a single code base. But every new application has a name like "project (ios)" or "project (android)". This looks confusing...

I also use the rename package so that I can specify an app nickname even without changing variables!

UPD: oh yep, it's called a "white label app"

[brunodmn]

I would like this option OR no nicknames at all.

My company develop white label applications, I use 1 firebase project to store 30 apps, all are listed with same nickname as I use flutterfire configure.

The problem with it, when some of these 30 apps has problems, per example, I cannot find the right one to check on Crashlytics, as all are listed with same name (the nickname).

Check below image, these are 7 differents apps I have under same firebase project:

As a workaround, I need first to go to project settings and rename the nickname (mostly I would set nickname same as package name). This way I would find it on Crashlytics, Analytics, and so on.

If nickname was optional my life would be a lot easier.

It is optional on firebase project settings, it makes no sense flutterfire configure set it by default.

[github-actions]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.