incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Hemker (JIRA)" <>
Subject [jira] [Created] (CB-1535) LocalStorage is not saved after first App launch on iOS 6
Date Tue, 25 Sep 2012 13:54:07 GMT
Christian Hemker created CB-1535:

             Summary: LocalStorage is not saved after first App launch on iOS 6
                 Key: CB-1535
             Project: Apache Cordova
          Issue Type: Bug
          Components: iOS
    Affects Versions: 2.1.0
         Environment: iOS 6.0 - iOS Simulator
iOS 6.0 - iPad 2
            Reporter: Christian Hemker
            Assignee: Shazron Abdullah

1. Save a value in window.localStorage after a fresh install of the App in Simulator or iOS
2. Stop the App while running in Background.
3. Restoring the value from window.localStorage is not possible (Error)
4. Save a new value in window.localStorage
5. Stop the App while running in Background.
6. Now you can restore the value (Everything runs fine from now on)

Simple Javascript Test code to reproduce with index.html

<script type="text/javascript">
            document.addEventListener("deviceready", onDeviceReadyToSave, false);
            function onDeviceReadyToSave() {
                var item = window.localStorage.getItem("key");
                var message = "deviceready localStorage.getItem('key')="+item+" localStorage.length="+window.localStorage.length;
                console.log( message);
                if( item == null){
                    console.log("localStorage.getItem('key') is '"+item+"'");
                    item = "";
                item = item + "value";
                window.localStorage.setItem("key", item);
                console.log("calling localStorage.setItem('key', '"+item+"')");
                var value = window.localStorage.getItem("key");
                console.log("verified localStorage.getItem('key')="+value);


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

View raw message