incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shazron Abdullah (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (CB-209) Improve ios upgrade procedure to take burden off of end developer
Date Mon, 06 Feb 2012 20:08:00 GMT


Shazron Abdullah resolved CB-209.

       Resolution: Fixed
    Fix Version/s: 1.4.0

Upgrade Guide solves this.
> Improve ios upgrade procedure to take burden off of end developer
> -----------------------------------------------------------------
>                 Key: CB-209
>                 URL:
>             Project: Apache Callback
>          Issue Type: Improvement
>          Components: iOS
>    Affects Versions: 1.3.0
>         Environment: IOS
>            Reporter: Gary Bentley
>            Assignee: Shazron Abdullah
>            Priority: Critical
>             Fix For: 1.4.0
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message