You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Shazron Abdullah (JIRA)" <ji...@apache.org> on 2016/06/30 03:44:12 UTC

[jira] [Assigned] (CB-11323) `cordova platform update ios` resets entire Xcode project

     [ https://issues.apache.org/jira/browse/CB-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shazron Abdullah reassigned CB-11323:
-------------------------------------

    Assignee: Shazron Abdullah

> `cordova platform update ios` resets entire Xcode project
> ---------------------------------------------------------
>
>                 Key: CB-11323
>                 URL: https://issues.apache.org/jira/browse/CB-11323
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 6.2.0
>         Environment: OSX 10.11.5
>            Reporter: Tom Bell
>            Assignee: Shazron Abdullah
>
> I run `cordova update platform ios` to make sure it's up to date. The platform is up to date, but running `cordova update platform ios` basically nukes the Xcode project and essentially creates a "new" project.
> This means the following gets removed/reset:
> * Plugins removed
> * Additional schemes removed
> * Modified source file changes removed
> This means we can't actually customise any native code for the platform without it getting reset by an update.
> If this is the case where the platform is some "dumb" base project, how are people expected to have different schemes and changes to native code?
> Are we expected to create a bunch of "hooks" that basically find/replace the code with our changes, not exactly user friendly?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org