New issue
Advanced search Search tips

Issue 294409 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2014
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

chrome.storage.local.set saves data in Chrome Storage, but when reloading the app, the data reverts to previous state

Reported by james.mo...@a-cti.com, Sep 18 2013

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.65 Safari/537.36

Steps to reproduce the problem:
1.  Store some data in Chrome storage  
2.  Reload the app.
3.  Run chrome.storage.local.get(null, function(ss) { s = ss; }); 
4.  inspect s in the console and note that the data reverts to previous state.

What is the expected behavior?
We expect the data saved to show up, not the data stored previously.

What went wrong?
The data saved in Chrome storage isn't staying saved when reloading the app.

Did this work before? Yes Until this latest release of Chrome Stable v29

Chrome version: 29.0.1547.65  Channel: n/a
OS Version: OS X 10.8.5
Flash Version: Shockwave Flash 11.8 r800

This occurs on a Macbook Air, but I haven't been able to replicate it on any other computers other than this machine.  I also made sure all other windows were closed in the app and even set the data manually from the console using chrome.storage.local.set before reloading.

I also tried a different browser profile, and we still experience the issue.

I don't know what you need to complete this, so let me know how I can help.
 

Comment 1 by meh...@chromium.org, Sep 19 2013

Labels: Cr-Platform-Apps
Owner: benwells@chromium.org
Status: Assigned
This is strange. I've been using chrome.storage.local recently without problem, and if it was broken I'd expect there to be a lot of bug reports.

I'm guessing there is something special either in your app or in your test setup. What happens if:
a) you set then get the data on the console without doing a reload?
b) you don't reload but close your app, wait twenty seconds (i.e. let its background page be unloaded) and then open it again?

Labels: Needs-Feedback
Status: ExternalDependency
James - is this still an issue?

Can you answer the questions above? An example app which shows the problem would be great; as we have had no other reports of this, if it is still happening it is probably something special about your app.
Status: WontFix
No other reports of this and no more info from reporter so marking WontFix. If there is more to add please reopen.

Sign in to add a comment