Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Date: Fri, 30 Mar 2012 16:24:28 +0000 (UTC)
From: "Filip Maj (Updated) (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: 
 <2010127437.38520.1333124668551.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1789556637.37723.1333113147501.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CB-414) When upgrading 1.4 app to 1.6.0rc1 on
 iOS5.1, still getting deny file-write-create error on window.openDatabase()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CB-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Filip Maj updated CB-414:
-------------------------

    Component/s:     (was: CordovaJS)
                 iOS
       Assignee: Shazron Abdullah  (was: Filip Maj)

Changing the component tagged, don't think this is a JS issue.
                
> When upgrading 1.4 app to 1.6.0rc1 on iOS5.1, still getting deny file-write-create error on window.openDatabase()
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: CB-414
>                 URL: https://issues.apache.org/jira/browse/CB-414
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 1.6.0
>         Environment: Cordova 1.6.0rc1, iOS5.1, Xcode 4.3
>            Reporter: Gabi Schaffzin
>            Assignee: Shazron Abdullah
>
> When calling window.openDatabase(), I'm still getting the "deny file-write-create /private/var/mobile/Applications/[XXXX]". 
> This *only* happens when upgrading the previous version of my app. It doesn't happen when debugging the app directly on the device from Xcode. Nor does it happen when I delete the app and install the Ad-Hoc version as new.
> I've tried calling window.openDatabase() on a completely new database (different name and identifier), but get the same error.
> Is there a way I can force the app _not_ to seek out that file?

--
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