incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neil Harding (JIRA)" <>
Subject [jira] [Commented] (CB-684) WebKit database restore on iOS5.1 corrupts large databases
Date Fri, 11 May 2012 10:07:55 GMT


Neil Harding commented on CB-684:

Thanks for your response. Obviously it's disappointing you're not going to look at this. Although
I understand we are an edge case but aside from this issue the app runs well with a large
database and in Phonegap 1.4.1 there was no issue. 

Could there at least be a hook somewhere to turn off the backup/restore process? We are developing
an enterprise app where we are in complete control of the iPads that are deployed to and can
stipulate that there should always be ample remaining space so iOS will never run low on space
and clear up the /library/caches folder. 

We want to continue with Cordova and benefit from api updates and bug fixes, but this is a
real blocker at sticks us at 1.4.1.
> WebKit database restore on iOS5.1 corrupts large databases
> ----------------------------------------------------------
>                 Key: CB-684
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 1.6.1
>         Environment: iOS5.1
>            Reporter: Neil Harding
>            Assignee: Shazron Abdullah
>            Priority: Critical
>              Labels: database, ios, sqlite, webkit
> The backup and restore process for WebKit databases on iOS5.1 to copy databases from
the /library/caches folder to /documents/backup is corrupting large databases. 
> I have a 1Gb sqllite databases, this is is because there will be a lot of data in the
app and to get around the 5mb quota limit for Websql databases on iOS a large pre populated
.db file is copied over to /library/caches on app start up in didFinishLaunchingWithOptions
if it doesn't already exist. This 'reserves' the footprint of the database as sqlite doesn't
unallocated space when deleting rows, the data is cleared out and the app can start off without
any quota errors.   
> When the app terminates and the backup process runs to copy the .db file to /documents/backup
it doesn't complete the process successfully (possibly killed by iOS before the file is fully
written?) and the resulting file .db is much smaller (~200mb) and corrupt.
> When the app runs next time the .db is copied from /documents/backup to /library/caches
ok, but the damage is already done.

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