[CB-209] Improve ios upgrade procedure to take burden off of end developer

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 1.4.0
• Component/s: cordova-ios

Environment

IOS

• Assignee: Shazron Abdullah
• Reporter: Gary Bentley
• Created: 31/Jan/12 05:01
• Updated: 23/Aug/18 07:45
• Resolved: 06/Feb/12 20:07

Description

Currently to upgrade phone gap to a new version it is recommended that you create a completely new phone gap project and then migrate your settings across to the new project.

This is problematic for a number of reasons:

1. There are many settings that have to be transfered, including splash images and icons, external hosts, code signing setup, orientations and more. It is onerous to have to manually set these up every time you want to use a new version of phone gap.

2. It breaks your source control since the new project is not under source control, it also breaks your archives within XCode.

Compare this with upgrading to a new phone gap version for Android where all you need to do is change the .jar and .js file.

Having to manually re-create your project for a new version in ios is a significant barrier and can be a huge time sync.

What is needed is an upgrade mechanism that is similar to Android, the end developer should not be re-creating a project for new versions.

Issue Links

• is related to: CB-168 Write upgrade guide on how to upgrade from 1.3.0 to > 1.4.0 (PhoneGap as a component changes)