Github user fredgalvao commented on the issue:
https://github.com/apache/cordova-ios/pull/228
Is there any reason why this PR doesn't also export `CFBundleName` as the
result of the short name on config.xml? Follow me for a while:
According to [this page on the developer
portal](https://developer.apple.com/library/content/qa/qa1892/_index.html) it
seems like these two properties go along and, unless they are too big, should
most probably have the same value.
Now, with the recent findings and issues related to renaming projects
(which causes malformed pbxproj files and unsolvable string search&replace
operations), it seems to me like we could simply leave the project structure
and project name (not to be confused with app name) a generic static value, and
deal with the `<name>` and `<short-name>` outputing them to
`CFBundleDisplayName` and `CFBundleName` respectively.
That's what I did when I evolved my cordova project into a whitelabel, so
that I could generate different apps with the same code base. However, in my
case I needed to use a string replacement on `build.gradle` to set the
`applicationId` on android (the app name works fine, it's updated in the
string.xml correctly and my main activity class doesn't need to be renamed).
There's an [issue](https://issues.apache.org/jira/browse/CB-11374) for the
`applicationId` thing too, btw. On iOS, I also had to use
[cordova-plugin-app-name](https://github.com/blakgeek/cordova-plugin-app-name/blob/master/plugin.xml)
to deal with the "renaming breaks the project" issue (leaving the `<name>`
untouched, otherwise I'd be screwed).
## Summary of my _opinion_
To evolve into a more whitelabel-friendly structure with respect to naming
apps:
- Evolve `<name>` and `<short-name>` handling to affect **ONLY**
{`strings.xml`@`app_name`} on android, and {`CFBundleName` +
`CFBundleDisplayName`} on iOS, leaving the following items with a generic
static name [activity class name on android, xcode project files (plist,
pbxproj)].
Please @shazron and @dpogue tell me what you think of all of this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
