Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Date: Wed, 21 Mar 2012 14:47:39 +0000 (UTC)
From: "Samuel Michelot (Issue Comment Edited) (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: 
 <2022361159.41814.1332341259938.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1175307527.13830.1331744920676.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Issue Comment Edited] (CB-330) localStorage / SQLDatabase
 no longer persistent after iOS 5.01 Update
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CB-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234388#comment-13234388 ] 

Samuel Michelot edited comment on CB-330 at 3/21/12 2:46 PM:
-------------------------------------------------------------

After some testing, it looks like the plugin doesn't do the migration from WebKit folder to the Caches folder. It should happens when users upgrade to iOS5.1 before that fix (before upgrading the app with the backup fix). I know that sometime, the WebKit folder is completely deleted during the iOS 5.1 update, but sometime, it's still there...

Here is an example of code to handle that migration : https://gist.github.com/2009491 (just for inspiration, because it migrate everything to the Document folder, it's for the PGSQLitePlugin)
                
      was (Author: mosamich):
    After some testing, it looks like the plugin doesn't do the migration from WebKit folder to the Caches folder. It should happens when users upgrade to iOS5.1. I know that sometime, the WebKit folder is completely deleted during the iOS5.1 update, but sometime, it's still there...

Here is an example of code to handle that migration : https://gist.github.com/2009491 (just for inspiration, because it migrate everything to the Document folder, it's for the PGSQLitePlugin)
                  
> localStorage / SQLDatabase no longer persistent after iOS 5.01 Update
> ---------------------------------------------------------------------
>
>                 Key: CB-330
>                 URL: https://issues.apache.org/jira/browse/CB-330
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 1.3.0, 1.4.0, 1.5.0
>         Environment: iOS 5.01
> PhoneGap (Any version)
> Xcode 4
> Build.PhoneGap
>            Reporter: Amirudin Bin Mohamed Ghani
>            Assignee: Shazron Abdullah
>            Priority: Blocker
>              Labels: ios5.01, localstorage, sqldatabase, websql
>             Fix For: 1.6.0
>
>         Attachments: CDVLocalStoragePlugin.zip, Directory-Structure-CB-330.zip, LocalStorageTest.zip, iOS WebKit Database Locations.txt
>
>
> Dear Dev
> WebKit data (localstorage or local SQLite) are now stored in Library/ Caches folder (instead of Library/WebKit folder). This is a big problem for all apps using UIWebView and storing user data, because they will no longer be backed up and may be deleted. There are a lot of apps using localstorage or SQLite as a critical feature. 
> The SQLite database gets deleted because the database is saved in a location on the filesystem which Apple does not consider to contain persistent data.
> *Steps to Reproduce:* 
> In a UIWebView, create a new DB or use localStorage with JavaScript. 
> You can see that the WebKit data is now stored in Library/Caches :  
> *Expected Results:*
> We should at least specify the directory of WebKit data (and to set it 
> to Documents/ for critical data) 
> *Actual Results:* 
> The WebKit data are stored in Library/Caches folder, and can be 
> deleted 
> *Regression:*
> To migrate database location from Library/Caches to some other location such as Documents.
> ----
> Ref: http://developer.apple.com/icloud/documentation/data-storage/
> https://devforums.apple.com/thread/137882?start=0&tstart=0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira