[
https://issues.apache.org/jira/browse/CB-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Farley updated CB-9500:
--------------------------------
Description:
The recent changes to the compile command (CB-8485) have introduced an issue on
iOS. Specifically, the inline creation of the signed archive, have made it
impossible to have an iOS applications display name be different from the
Cordova project name.
The archive generation process expects the .app name to have the same basename
as the name listed in the XCodeProject. If it does not find the .app at this
position, it fails the conversion and the entire compile process.
The .app it creates is based upon the Cordova project name. The name in the
XCodeProject is the name used for applications name when it is on a device, so
now this name must match the project name or the signed archive won't be
created.
This can be fixed in a number of ways.
- Include a "no-sign" option, which would mimic the old behavior.
- Include a way to pass the desired name to compile.
- Have the .app name be pulled from some other configuration that isn't tied
to a the iOS display name.
was:
The recent changes to the compile command (CB-8485) have introduced an issue on
iOS. Specifically, the inline app-to-ipa conversion have made it impossible to
have an iOS applications display name be different from the Cordova project
name.
The conversion process expects the .app name to have the same basename as the
name listed in the XCodeProject. If it does not find the .app at this position,
it fails the conversion and the entire compile process.
The .app it creates is based upon the Cordova project name. The name in the
XCodeProject is the name used for applications name when it is on a device, so
now this name must match the project name or conversion won't work.
This can be fixed in a number of ways.
- Include a "no-conversion" option, which would mimic the old behavior.
- Include a way to pass the desired name to compile.
- Have the .app name be pulled from some other configuration that isn't tied
to a the iOS display name.
> [CB-8485] Not allowed to have XCodeProject display name different from
> Cordova project name
> -------------------------------------------------------------------------------------------
>
> Key: CB-9500
> URL: https://issues.apache.org/jira/browse/CB-9500
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Affects Versions: 5.2.0
> Environment: Mac OS X
> Reporter: Nicholas Farley
> Priority: Minor
> Labels: compile, compile-error, compilerconfiguration,
> conversion, error, ios, name, xcode
> Fix For: 5.2.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The recent changes to the compile command (CB-8485) have introduced an issue
> on iOS. Specifically, the inline creation of the signed archive, have made it
> impossible to have an iOS applications display name be different from the
> Cordova project name.
> The archive generation process expects the .app name to have the same
> basename as the name listed in the XCodeProject. If it does not find the .app
> at this position, it fails the conversion and the entire compile process.
> The .app it creates is based upon the Cordova project name. The name in the
> XCodeProject is the name used for applications name when it is on a device,
> so now this name must match the project name or the signed archive won't be
> created.
> This can be fixed in a number of ways.
> - Include a "no-sign" option, which would mimic the old behavior.
> - Include a way to pass the desired name to compile.
> - Have the .app name be pulled from some other configuration that isn't tied
> to a the iOS display name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
