[
https://issues.apache.org/jira/browse/CB-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354842#comment-15354842
]
Shazron Abdullah edited comment on CB-11323 at 6/30/16 3:41 AM:
----------------------------------------------------------------
More than just "plugins" are reset.
Upgrading to 4.2.0:
1. Removed my custom schemes
2. Removed my 3rd party frameworks
3. Removed my 3rd party assets
4. Reset icon assets to Cordova ones
5. Reset splash screen assets to Cordova ones
6. Removed changes I had made to the view controller
The idea that the native parts aren't supposed to be modified basically reduces
Cordova to a really bad project. This was all fine previously until the major
version bumps.
was (Author: tombell):
More than just "plugins" are reset.
Upgrading to 4.2.0:
* Removed my custom schemes
* Removed my 3rd party frameworks
* Removed my 3rd party assets
* Reset icon assets to Cordova ones
* Reset splash screen assets to Cordova ones
* Removed changes I had made to the view controller
The idea that the native parts aren't supposed to be modified basically reduces
Cordova to a really bad project. This was all fine previously until the major
version bumps.
> `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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
